[
https://issues.apache.org/jira/browse/OAK-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720303#comment-14720303
]
Manfred Baedke commented on OAK-3263:
-------------------------------------
[~tmueller],
bq. I think no. Let's say the query is /jcr:root/a//*[@x=1], the data is (each
node listed has the property "x" set to 1): /a, /a/b, /a/b/c. The index would
not include /a/b/c because that is excluded (right?), so the query would not
return /a/b/c when using that index. If the index is not used, /a/b/c is
returned correctly.
This is true. On the other hand, what's the point then of allowing includedPath
that are ancestors of excludedPath?
> Support including and excluding paths for PropertyIndex
> -------------------------------------------------------
>
> Key: OAK-3263
> URL: https://issues.apache.org/jira/browse/OAK-3263
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Chetan Mehrotra
> Assignee: Manfred Baedke
> Labels: doc-impacting, performance
> Fix For: 1.3.6
>
> Attachments: OAK-3263-b.patch, OAK-3263-prelimary.patch,
> OAK-3263-v2.patch, OAK-3263.patch
>
>
> As part of OAK-2599 support for excluding and including paths were added to
> Lucene index. It would be good to have such a support enabled for
> PropertyIndexe also
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
