[jira] [Commented] (OAK-2134) Lucene: not using the path restriction can speed up queries

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

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

Chetan Mehrotra commented on OAK-2134:
--------------------------------------

bq. also index all parent paths of a node (not store those in the document; just index them); when querying, use an exact match for the parent.

For this we can probably use the [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

> Lucene: not using the path restriction can speed up queries
> -----------------------------------------------------------
>
>                 Key: OAK-2134
>                 URL: https://issues.apache.org/jira/browse/OAK-2134
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: oak-lucene
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 1.1.0, 1.0.7
>
>
> Currently, the Oak Lucene index uses the path restriction in the hope that queries can be faster. However, I found that not using the path restriction is better (much better) in many cases. The following queries were run:
> {noformat}
> :fulltext:test
> +:fulltext:test +:path:/path/prefix/*
> {noformat}
> A workaround is to change the query, by removing the path restriction, and adding a 'like' conditions, as follows (for XPath):
> {noformat}
> ... and jcr:like(@jcr:path, '/path/prefix/%')
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)