[
https://issues.apache.org/jira/browse/LUCENE-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343161#comment-14343161
]
Jan Høydahl edited comment on LUCENE-5833 at 3/2/15 1:45 PM:
-------------------------------------------------------------
I did some testing with multi valued {{field}} input, and random {{weight}}
input between 0-100 for the docs in the index. What seems to happen then is
that the suggester outputs one suggestion per unique weight:
{code}
{
"suggest":{"languages":{
"engl":{
"numFound":101,
"suggestions":[{
"term":"<b>Engl</b>ish",
"weight":100,
"payload":"0"},
{
"term":"<b>Engl</b>ish",
"weight":99,
"payload":"0"},
{
"term":"<b>Engl</b>ish",
"weight":98,
"payload":"0"},
---etc all the way down to 0---
{code}
Using Solr with {{BlendedInfixLookupFactory}}. Can anyone explain this
behavior? I tested on solr5.0.0
was (Author: janhoy):
I did some testing with multi valued {{field}} input, and random {{weight}}
input between 0-100 for the docs in the index. What seems to happen then is
that the suggester outputs one suggestion per unique weight:
{code}
{
"suggest":{"languages":{
"engl":{
"numFound":101,
"suggestions":[{
"term":"<b>Engl</b>ish",
"weight":100,
"payload":"0"},
{
"term":"<b>Engl</b>ish",
"weight":99,
"payload":"0"},
{
"term":"<b>Engl</b>ish",
"weight":98,
"payload":"0"},
---etc all the way down to 0---
{code}
Using Solr with {{BlendedInfixLookupFactory}}. Can anyone explain this behavior?
> Suggestor Version 2 doesn't support multiValued fields
> ------------------------------------------------------
>
> Key: LUCENE-5833
> URL: https://issues.apache.org/jira/browse/LUCENE-5833
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/other
> Affects Versions: 4.8.1
> Reporter: Greg Harris
> Assignee: Erick Erickson
> Fix For: 5.0, Trunk
>
> Attachments: LUCENE-5833.patch, LUCENE-5833.patch, LUCENE-5833.patch,
> LUCENE-5833_branch4_10.patch, SOLR-6210.patch
>
>
> So if you use a multiValued field in the new suggestor it will not pick up
> terms for any term after the first one. So it treats the first term as the
> only term it will make it's dictionary from.
> This is the suggestor I'm talking about:
> https://issues.apache.org/jira/browse/SOLR-5378
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
