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 "Jukka Zitting (JIRA)" <ji...@apache.org> on 2014/08/18 18:00:22 UTC

[jira] [Commented] (OAK-2005) Use separate Lucene index for performing property related queries

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

Jukka Zitting commented on OAK-2005:
------------------------------------

Is there a particular reason not to use a single Lucene index for both full text and property queries? There are often queries that combine both types of constraints, so having a single index that can evaluate both types would be beneficial.

> Use separate Lucene index for performing property related queries 
> ------------------------------------------------------------------
>
>                 Key: OAK-2005
>                 URL: https://issues.apache.org/jira/browse/OAK-2005
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: oak-lucene
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.1
>
>         Attachments: OAK-2005-1.patch
>
>
> Oak Lucene has some support for working with multiple Lucene directories. Currently Oak uses a single Lucene directory to store the full text index. It would be worthwhile to investigate if we can use a separate Lucene index to store specific properties only and use it to perform property related queries.
> * A separate Lucene directory would be used to store explicitly configured list of properties
> * The properties would be stored with there type
> ** JCR Long - long
> ** JCR Double - double
> ** JCR Date - long - The data value can be stored in long but with lesser precision say upto second or even minutes
> * The values would stored "as is" i.e. without tokenization
> Possible benefits of such an index would be (ofcourse need be validated!)
> * Compact storage - Less memory would be used to store the index
> * Native support for Order By
> * Improved performance for like query - Specifically 'foo%', '%foo'



--
This message was sent by Atlassian JIRA
(v6.2#6252)