d" postings list for prefix
> > > terms. So instead of iterating over all terms and merging their
> postings,
> > > the terms dictionary could return a "virtual term" that contains all
> > > documents for a whole prefix and store the merged posti
t; > could create an improved BlockTermsDict implementation, that allows to get
> > a PostingsEnum for a whole prefix of terms.
> > >>
> > >> Not sure how much of that was already implemented by LUCENE-5879, but
> > it allows to do this. So here is where you coul
n and improve the
> terms dictionary!
> >>
> >> Uwe
> >>
> >> > Uwe
> >> >
> >> > -
> >> > Uwe Schindler
> >> > Achterdiek 19, D-28357 Bremen
> >> > http://www.thetaphi.de
> >> > eMail: u..
ut it
>> allows to do this. So here is where you could step in and improve the terms
>> dictionary!
>>
>> Uwe
>>
>> > Uwe
>> >
>> > -
>> > Uwe Schindler
>> > Achterdiek 19, D-28357 Bremen
>> > http://www.thetap
could step in and improve the terms
> dictionary!
>
> Uwe
>
> > Uwe
> >
> > -
> > Uwe Schindler
> > Achterdiek 19, D-28357 Bremen
> > http://www.thetaphi.de
> > eMail: u...@thetaphi.de
> >
> > > -Original Message-
> >
u could step in and improve the terms dictionary!
Uwe
> Uwe
>
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: Robert Muir
> > Sent: Monday, April 1, 2019
va-user
> Subject: Re: Clarification regarding BlockTree implementation of
> IntersectTermsEnum
>
> The regular TermsEnum is really designed for walking terms in linear order.
> it does have some ability to seek/leapfrog. But this means paths in a query
> automaton that match
The regular TermsEnum is really designed for walking terms in linear order.
it does have some ability to seek/leapfrog. But this means paths in a query
automaton that match no terms result in a wasted seek and cpu, because the
api is designed to return the next term after regardless.
On the other
Yes it is used.
I think there are simpler and possibly more efficient ways to implement a
TermRangeQuery and that is why I am looking into this.
But I am also curious to understand what IntersectTermsEnum is supposed to
do.
Στις Δευ, 1 Απρ 2019 στις 5:34 μ.μ., ο/η Robert Muir
έγραψε:
> Is this
Is this IntersectTermsEnum really being used for term range query? Seems
like using a standard TermsEnum, seeking to the start of the range, then
calling next until the end would be easier.
On Mon, Apr 1, 2019, 10:05 AM Stamatis Zampetakis wrote:
> Hi all,
>
> I am currently working on improving
10 matches
Mail list logo
