t; >
> > > On the other hand the intersect() is for intersecting two automata:
> query
> > > and index. Presumably it can also remove more inefficiencies than just
> the
> > > wasted seeks for complex wildcards and fuzzies and stuff, since it can
> &
only one posting for a term, that single
> posting is inlined directly into the term dictionary and often a
> ton of terms fit into this category, so seeing 80% time in the term
> dictionary wouldn't surprise me.
>
> On Tue, Apr 2, 2019 at 8:03 AM Stamatis Zampetakis
>
y sort by the field normally (with or without
> searchAfter)
>
> On Tue, Apr 2, 2019 at 7:34 AM Stamatis Zampetakis
> wrote:
> >
> > Thanks for the explanation regarding IntersectTermsEnum.next(). I
> > understand better now.
> >
> > How about indexing a st
:
> 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,
>
Hi all,
I am currently working on improving the performance of range queries on
strings. I've noticed that using TermRangeQuery with low-selective queries
is a very bad idea in terms of performance but I cannot clearly explain why
since it seems related with how the IntersectTermsEnum#next method
t;
> I personally like the current way things work. If we added the ability
> to set a custom score on ConstantScoreQuery, then we'd end up with two
> ways to do the same thing, which I like to avoid whenever possible.
>
> On Sun, Dec 8, 2019 at 10:07 PM Stamatis Zampetakis
> wrote
Small reminder. Any input on this?
Thanks,
Stamatis
On Mon, Dec 2, 2019 at 12:10 PM Stamatis Zampetakis
wrote:
> Hi all,
>
> Currently ConstantScoreQuery [1] returns a constant score equal to 1 for
> every document that matches the query.
>
> I would like to use the
your code. I don't
> understand why we would need separate query classes for this.
>
> Uwe
>
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: Stamatis Z
Hi all,
In the world of relational databases and SQL, the existence of
parameterized queries (aka. PreparedStatement) offers many advantages in
terms of security and performance.
I guess everybody is familiar with the idea that you prepare a statement
and then you execute it multiple times by
Visitor.
>
> On Wed, 23 Oct 2019 at 17:52, Stamatis Zampetakis
> wrote:
>
> > Hi Adrien,
> >
> > Are there optimizations based on statistics that take place during the
> > construction process of the query?
> >
> > When the query is about to be exe
> execute this query before knowing what the value of `a.name` is.
> Supporting something like that would send the message that it makes
> things more efficient while in practice it would only save a couple
> object creations.
>
> On Wed, Oct 23, 2019 at 9:26 AM Stamatis Zampetaki
databases expose.
>
> Atri
>
> On Mon, 21 Oct 2019 at 17:42, Stamatis Zampetakis
> wrote:
>
> > Hi al
> > In the world of relational databases and SQL, the existence of
> > parameterized queries (aka. PreparedStatement) offers many advantages in
> > ter
Hi all,
Currently ConstantScoreQuery [1] returns a constant score equal to 1 for
every document that matches the query.
I would like to use the ConstantScoreQuery but with a different score value
that I can pass explicitly (via the constructor for instance).
This change may also benefit some
> proven wrong though, if we can cheaply rewrite the expanded form, this
> would be a good addition.
>
> On Mon, Mar 30, 2020 at 6:06 PM Stamatis Zampetakis
> wrote:
>
> > Hi all,
> >
> > My question concerns the method setMinimumNumberShouldMatch in
> BooleaQuer
Hi all,
My question concerns the method setMinimumNumberShouldMatch in BooleaQuery
class.
Lets assume that we have 3 queries (optional clauses), namely A, B, C and
we build a BooleanQuery specifying that at least 2 should match.
In terms of semantics what I understand so far is that
(A B C)~2
>> C. (current logo)
> >>
> >> Andi.. (pmc)
> >>
> >>> On Jun 15, 2020, at 15:08, Ryan Ernst >>> <mailto:r...@iernst.net>> wrote:
> >>>
> >>>
> >
16 matches
Mail list logo
