Description
XPath queries such as
/jcr:root/a//b/c/d/*[@type='1' or @type='2']
are slow because they don't currently use an index on the property "type".
They are converted to a join, with selectors a joining b joining c and so on. Maybe it would be better to join in reverse order, or the query engine might need to reverse join order in this case (once an index is used).
Attachments
Issue Links
- is blocked by
-
OAK-1389 Query: an index is used even where traversing is faster
-
- Closed
-