[
https://issues.apache.org/jira/browse/OAK-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718195#comment-14718195
]
Thomas Mueller commented on OAK-3263:
-------------------------------------
About the "queryPaths": I think I remember now how it was used for Lucene
indexes. So I think we should use it here as well. I suggest to use it as
follows: if "queryPaths" is set, then this index is used for all queries within
those paths. If it is not there, then "includePaths" and "excludePaths" are
used to decide whether to use that index.
That way, it is possible to "force" using the index, by setting "queryPaths",
even for queries where that alters the result (possibly returns the wrong
result). Because of that, usually this property should not be used. It should
only be used temporarily for tests, or to work around performance problems,
without having to change the application. Using this property is dangerous,
because it can make queries return the wrong results.
I think this is not exactly how it is used for Lucene indexes right now, but I
think the Lucene index implementation should be changed to do the above. Also,
this needs to be documented.
> 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)
