Re: index selection when 0 or 1 property clause (or sort clause) matches

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

On Wed, May 17, 2017 at 1:40 PM, Alvaro Cabrerizo <to...@gmail.com> wrote:
> The main issue of delegating in entryCount, is that if the index contains
> more than 1000 docs and the query does not contain fulltext clauses the
> index planner will use the number *1000 *as the entryCount, ovewriting the
> actual size of the index [Math.min(definition.getEntryCount(), getReader().
> *numDocs())*].

A very late reply here but I have opened OAK-6333 to remove this
artificial limit of 1000 in cost estimates. Once we have consensus on
the approach then I would fix and backport it to older branched

Chetan Mehrotra

Re: index selection when 0 or 1 property clause (or sort clause) matches

[Alvaro Cabrerizo <to...@gmail.com>]

Good news is always welcome!

Many thanks Chetan.



On Fri, Jun 9, 2017 at 9:44 AM, Chetan Mehrotra <ch...@gmail.com>
wrote:

> On Wed, May 17, 2017 at 1:40 PM, Alvaro Cabrerizo <to...@gmail.com>
> wrote:
> > The main issue of delegating in entryCount, is that if the index contains
> > more than 1000 docs and the query does not contain fulltext clauses the
> > index planner will use the number *1000 *as the entryCount, ovewriting
> the
> > actual size of the index [Math.min(definition.getEntryCount(),
> getReader().
> > *numDocs())*].
>
> A very late reply here but I have opened OAK-6333 to remove this
> artificial limit of 1000 in cost estimates. Once we have consensus on
> the approach then I would fix and backport it to older branched
>
> Chetan Mehrotra
>