jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3263) Support including and excluding paths for PropertyIndex
Date Tue, 01 Sep 2015 08:54:46 GMT

    [ https://issues.apache.org/jira/browse/OAK-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725004#comment-14725004
] 

Thomas Mueller commented on OAK-3263:
-------------------------------------

> On the other hand, what's the point then of allowing includedPath that are ancestors
of excludedPath?

I guess we can't really "reject" a specific configuration. We can only log a warning if a
strange configuration is detected (for example, excludePaths equals to includePaths). A possible
use case I could imagine includePath = "/content", excludePath = "/content/dam". So that queries
on "/content/pages" and "/content/images" and so on are supported, but not on "/content/dam"
and "/content".

> 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)

Mime
View raw message