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/12/11 07:35:12 UTC

[jira] [Resolved] (OAK-2278) Same Lucene index to support both property restrictions and fulltext constraints

     [ https://issues.apache.org/jira/browse/OAK-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra resolved OAK-2278.
----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.2)
                   1.1.4
                   1.0.9

All subtask complete. Only pending task is about documentation. Resolving this issue

> Same Lucene index to support both property restrictions and fulltext constraints
> --------------------------------------------------------------------------------
>
>                 Key: OAK-2278
>                 URL: https://issues.apache.org/jira/browse/OAK-2278
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: oak-lucene
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.0.9, 1.1.4
>
>
> Currently oak-lucene has two indexes
> * LuceneIndex - For fulltext constraints and runtime aggregation
> * LucenePropertyIndex - For property restriction
> To support all the relevant JCR queries we should have a single LuceneIndex implementation supporting both fulltext and property restriction. Such an index would be using index time aggregation (OAK-2268) and would support
> # Fulltext constraint evaluation
> # Property restriction evaluation
> # Ordering/Sorting
> # Indextime aggregation



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