[
https://issues.apache.org/jira/browse/OAK-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840224#comment-13840224
]
Jeff Young commented on OAK-1215:
---------------------------------
C is constant when the query is run, but not when the index is built. A
project author will set up several predicates in some user interface; for
instance:
{code}
size
S
M
L
color
Red
Blue
{code}
and then a marketing person will run the various queries to find the products
they want to modify/annotate/whatever.
While the JCR application doesn't know the structure of things, the project
author does, so if what to index is configurable they could conceivably set it
up to index size and color (at the various depths). So ideally the search
would make use of the indexes -- but I'm not sure if it's a deal-breaker if it
doesn't do so in the first release. (A lot of that would depend on whether the
performance was a regression from Jackrabbit 2.x or not.)
> Relative property paths don't work in XPath search expressions
> --------------------------------------------------------------
>
> Key: OAK-1215
> URL: https://issues.apache.org/jira/browse/OAK-1215
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Jeff Young
> Priority: Critical
> Attachments: relative-predicate-paths.tiff
>
>
> A search XPath of the form:
> {code}
> /jcr:root/etc/commerce/products//*[@size='M' or */@size='M']
> {code}
> returns:
> {code}
> Invalid path: *
> {code}
> (This works fine in Jackrabbit.)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
