Hello,

I picked two first questions for reply.


> does this class offer any Shingling capability embedded to it?
>
No, it doesn't allow to expand wildcard phrase with shingles.


> I could not find any api within this class ComplexPhraseQueryParser for
> that purpose.
>

There are no one.




> Best regards
>
> On 2/4/20 11:14 AM, baris.ka...@oracle.com wrote:
> >
> > Thanks but i thought this class would have a mechanism to fix this issue.
> > Thanks
> >
> >> On Feb 4, 2020, at 4:14 AM, Mikhail Khludnev <m...@apache.org> wrote:
> >>
> >> It's slow per se, since it loads terms positions. Usual advices are
> >> shingling or edge ngrams. Note, if this is not a text but a string or
> enum,
> >> it probably let to apply another tricks. Another idea is perhaps
> >> IntervalQueries can be smarter and faster in certain cases, although
> they
> >> are backed on the same slow positions.
> >>
> >>> On Tue, Feb 4, 2020 at 7:25 AM <baris.ka...@oracle.com> wrote:
> >>>
> >>> How can this slowdown be resolved?
> >>> is this another limitation of this class?
> >>> Thanks
> >>>
> >>>>> On Feb 3, 2020, at 4:14 PM, baris.ka...@oracle.com wrote:
> >>>> Please ignore the first comparison there. i was comparing there
> {term1
> >>> with 2 chars} vs {term1 with >= 5 chars + term2 with 1 char}
> >>>>
> >>>> The slowdown is
> >>>>
> >>>> The query "term1 term2*" slows down 400 times (~1500 millisecs)
> compared
> >>> to "term1*" when term1 has >5 chars and term2 is still 1 char.
> >>>> Best regards
> >>>>
> >>>>
> >>>>> On 2/3/20 4:13 PM, baris.ka...@oracle.com wrote:
> >>>>> Hi,-
> >>>>>
> >>>>> i hope everyone is doing great.
> >>>>>
> >>>>> I saw this issue with this class such that if you search for "term1*"
> >>> it is good, (i.e., 4 millisecs when it has >= 5 chars and it is ~250
> >>> millisecs when it is 2 chars)
> >>>>> but when you search for "term1 term2*" where when term2 is a single
> >>> char, the performance degrades too much.
> >>>>> The query "term1 term2*" slows down 50 times (~200 millisecs)
> compared
> >>> to "term1*" case when term 1 has >5 chars and term2 is still 1 char.
> >>>>> The query "term1 term2*" slows down 400 times (~1500 millisecs)
> >>> compared to "term1*" when term1 has >5 chars and term2 is still 1 char.
> >>>>> Is there any suggestion to speed it up?
> >>>>>
> >>>>> Best regards
> >>>>>
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> >>>>> For additional commands, e-mail: java-user-h...@lucene.apache.org
> >>>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> >>>> For additional commands, e-mail: java-user-h...@lucene.apache.org
> >>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> >>> For additional commands, e-mail: java-user-h...@lucene.apache.org
> >>>
> >>>
> >> --
> >> Sincerely yours
> >> Mikhail Khludnev
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>

-- 
Sincerely yours
Mikhail Khludnev

Reply via email to