You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/11/29 17:29:12 UTC
[jira] [Comment Edited] (OAK-2280) Support path restriction in
IndexPlanner
[ https://issues.apache.org/jira/browse/OAK-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228822#comment-14228822 ]
Chetan Mehrotra edited comment on OAK-2280 at 11/29/14 4:28 PM:
----------------------------------------------------------------
Required work for getting testcase passed done. Complete solution would be implemented as part of OAK-2306
was (Author: chetanm):
Required work for getting testcase passed done. Complete solution would be implemented as part of OAK-2280
> Support path restriction in IndexPlanner
> ----------------------------------------
>
> Key: OAK-2280
> URL: https://issues.apache.org/jira/browse/OAK-2280
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: oak-lucene
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.0.9, 1.1.3
>
>
> {{LucenePropertyIndex}} has some support for evaluating path restrictions. This has been restricted recently with OAK-2134. Currently some testcase make test with path based queries.
> To pass those test we add support for providing a plan if path restriction is present and no other property restriction is present. This features needs to be enabled explcitly via config option.
> Later we can provide a more performant by using [PathHierarchyTokenizer|http://lucene.apache.org/core/4_6_1/analyzers-common/org/apache/lucene/analysis/path/PathHierarchyTokenizer.html] and see how much it increases the index size
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)