Re: Extending the IndexPlan with custom data

[Marcel Reutegger <mr...@adobe.com>]

Hi,

as part of OAK-1980 I recently extended the IndexPlan with additional
methods like getDefinition(). This method returns the NodeState of the
index definition and allows you to identify the associated index in
content when the plan is executed. Maybe this is already sufficient for
your requirement?

Regards
 Marcel

On 31/07/14 12:57, "Chetan Mehrotra" <ch...@gmail.com> wrote:

>Hi,
>
>While working on multiple Lucene index support (OAK-2005) I need to
>make LuceneIndex implement the AdvanceQueryIndex. As part of OAK-2005
>we would be having multiple Lucene indexes where each index would be
>configured to store different types of data.
>
>As part of getPlans call LuceneIndex would be returning multiple
>IndexPlans depending on which index meet the Filter criteria upto what
>level. In doing that LuceneIndex would have already determined the
>Lucene index it can use for that plan. This information can then be
>used to pickup the required Index when actual {{query}} method is
>invoked with given plan
>
>Would it be ok to provide a custom impl of IndexPlan which embeds
>LuceneIndex related custom data like which index to use for this plan?
>Would it be safe to assume that IndexPlan instance returned from the
>getPlans call would be passed back in the {{query}} call?
>
>Chetan Mehrotra

Re: Extending the IndexPlan with custom data

[Chetan Mehrotra <ch...@gmail.com>]

On Tue, Aug 19, 2014 at 11:59 AM, Marcel Reutegger <mr...@adobe.com> wrote:
> Maybe this is already sufficient for
> your requirement?

Yup that would serve the purpose. For now I do not require that
support after following Thomas suggestion about using one index per
implementation. So for multiple Lucene index defintions multiple
LuceneIndex instances would be returned by LucenIndexProvider and each
impl would return a single plan


Chetan Mehrotra