On Tue, Aug 19, 2014 at 11:59 AM, Marcel Reutegger 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 def
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 requirem
On Thu, Jul 31, 2014 at 7:01 PM, Tommaso Teofili
wrote:
> as far as I know one workaround to trigger usage of a specific index is to
> use the native language supported by that specific index, but then that, of
> course, would require writing the query in a implementation specific way
> (e.g. sele
2014-07-31 15:20 GMT+02:00 Chetan Mehrotra :
> On Thu, Jul 31, 2014 at 5:23 PM, Thomas Mueller wrote:
> > You could simply have *multiple* index instances, and each index returns
> > its own cost or plan(s). The query engine will figure out which index to
> > use.
>
> Aah missed the fact that Que
On Thu, Jul 31, 2014 at 5:23 PM, Thomas Mueller wrote:
> You could simply have *multiple* index instances, and each index returns
> its own cost or plan(s). The query engine will figure out which index to
> use.
Aah missed the fact that QueryProvider can return multiple indexes.
That would simpli
Hi,
I'm not quite sure what you are trying to do. You don't need to do the
multiplexing *within* your index. Let the query engine do the multiplexing.
> Would it be safe to assume that IndexPlan instance returned from the
>getPlans call would be passed back in the {{query}} call?
Yes, the index
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 woul
