[
https://issues.apache.org/jira/browse/OAK-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716729#comment-14716729
]
Manfred Baedke commented on OAK-3263:
-------------------------------------
[~tmueller],
bq. I would switch the logic here ((if filter == INCLUDE) return null), but
then, it looks wrong to me... Is it really correct?
If it's wrong here, then it's also wrong in LucenIndexEditor - the methods are
semantically equivalent. But why do you think it isn't right? Could you
elaborate?
> 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: 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)
