[
https://issues.apache.org/jira/browse/OAK-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-2119:
---------------------------------
Attachment: OAK-2119.patch
Patch for the same. It introduces following changes
* IndexPlan.copy - Added a method to clone the IndexPlan so that one can pass
plan with different filters while creating different cursors in AggregateIndex.
This is similar to what we do earlier in
{{AggregateIndex.newAggregationFilter}} where we do a _copy_ of Filter.
* AdvanceFulltextQueryIndex - Introduced a new Advance counterpart of
{{FulltextQueryIndex}}
* Cost calculation - As both baseIndex and AggregateIndex would not be present
in an Oak system at same time and only AggregateIndex would be present it
should ok to just delegate the baseIndex for cost and plan determinination.
[~tmueller] and [~alexparvulescu] Can you have a look at the patch
> AggregateIndex should support AdvanceQueryIndex
> -----------------------------------------------
>
> Key: OAK-2119
> URL: https://issues.apache.org/jira/browse/OAK-2119
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Chetan Mehrotra
> Fix For: 1.1, 1.0.7
>
> Attachments: OAK-2119.patch
>
>
> Currently AggregateIndex is based on FulltextQueryIndex and thus support
> default QueryIndex. With OAK-2005 LuceneIndex would be implementing the
> {{AdvanceQueryIndex}}. To support that {{AggregateIndex}} should also support
> {{AdvanceQueryIndex}} based {{FulltextQueryIndex}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
