lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <erickerick...@gmail.com>
Subject Re: [jira] [Commented] (LUCENE-8347) BlendedInfixSuggester to handle multi term matches better
Date Fri, 07 Sep 2018 15:14:45 GMT
The branches where development happens are master and branch_7x.
Typically we pull and work on master and whoever commits it backports
to 7x if appropriate.

So from your perspective, if you're doing development just use "master".

If you're trying to patch your local version, pull that branch. For
instance, if you're working on Solr 7.2.1, then pull branch_7_2

Best,
Erick
On Fri, Sep 7, 2018 at 2:46 AM Akshay Patil (JIRA) <jira@apache.org> wrote:
>
>
>     [ https://issues.apache.org/jira/browse/LUCENE-8347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606902#comment-16606902
]
>
> Akshay Patil commented on LUCENE-8347:
> --------------------------------------
>
> Hello,
>
>
>
> I am new to this repository. I would like to apply the patch. would you please tell me
the right branch to pull to eclipse. Because, there are so many branches and I am confused
in order to build.
>
>
>
> Any help regarding solr blendedsuggester would be approciated.
>
>
>
>
>
> Best Regards !
>
>
>
>
>
> > BlendedInfixSuggester to handle multi term matches better
> > ---------------------------------------------------------
> >
> >                 Key: LUCENE-8347
> >                 URL: https://issues.apache.org/jira/browse/LUCENE-8347
> >             Project: Lucene - Core
> >          Issue Type: Improvement
> >          Components: core/search
> >    Affects Versions: 7.3.1
> >            Reporter: Alessandro Benedetti
> >            Priority: Major
> >         Attachments: LUCENE-8347.patch, LUCENE-8347.patch
> >
> >
> > Currently the blendedInfix suggester considers just the first match position when
scoring a suggestion.
> > From the lucene-dev mailing list :
> > "
> > If I write more than one term in the query, let's say
> >
> > "Mini Bar Fridge"
> >
> > I would expect in the results something like (note that allTermsRequired=true and
the schema weight field always returns 1000)
> >
> > - *Mini Bar Fridge* something
> > - *Mini Bar Fridge* something else
> > - *Mini Bar* something *Fridge*
> > - *Mini Bar* something else *Fridge*
> > - *Mini* something *Bar Fridge*
> > ...
> >
> > Instead I see this:
> >
> > - *Mini Bar* something *Fridge*
> > - *Mini Bar* something else *Fridge*
> > - *Mini Bar Fridge* something
> > - *Mini Bar Fridge* something else
> > - *Mini* something *Bar Fridge*
> > ...
> >
> > After having a look at the suggester code (BlendedInfixSuggester.createCoefficient),
I see that the component takes in account only one position, which is the lowest position
(among the three matching terms) within the term vector ("mini" in the example above) so all
the suggestions above have the same weight
> > "
> > Scope of this Jira issue is to improve the BlendedInfix to better manage those scenarios.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message