[
https://issues.apache.org/jira/browse/OAK-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720312#comment-14720312
]
Manfred Baedke commented on OAK-3263:
-------------------------------------
bq. 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.
Makes sense to me.
> 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)
