that at all. As the baseIndex is not
registered with Oak going for such finer cost calculation is probably
not required. We can just propagate the baseIndex plans
I have updated a patch to OAK-2119 which changes AggregateIndex to
implement AdvanceQueryIndex. With those changes (and related
calculation is probably
not required. We can just propagate the baseIndex plans
I have updated a patch to OAK-2119 which changes AggregateIndex to
implement AdvanceQueryIndex. With those changes (and related changes
in Lucene) all test pass fine. If it looks fine I can go ahead with my
change and move
Hi,
For Lucene based property index (OAK-2005) I need to make LuceneIndex
implement AdvanceQueryIndex. As AggregateIndex (AI) wrap LuceneIndex
(for FullText search) it would also need to be adapted to support the
same (OAK-2119). However making it do that seems bit tricky
A - Cost aggregation
