[
https://issues.apache.org/jira/browse/LUCENE-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341745#comment-14341745
]
Jan Høydahl edited comment on LUCENE-5833 at 2/28/15 10:12 PM:
---------------------------------------------------------------
As a *Lucene* issue, this is probably not a bug. However it started as a *SOLR*
issue, where it appears more like a bug:
The Solr ref guide does not document the single-value only constraint; in fact
it encourages using copyField to populate the "field" to use for suggestions,
which in fact requires multiValued=true. So we can either treat it as a (Solr)
bug and backport this issue, or add a (Solr) patch which adds a warning or
exception when attempting to use multiVal; or treat it as a (Solr)
documentation bug and add a note in refguide [Errata
page|https://cwiki.apache.org/confluence/display/solr/Errata] for 4.10.x. I'm
happy with any of these, my customer who got bit by this can run a patched
version if need be.
Perhaps there should have been a separate SOLR issue for this?
was (Author: janhoy):
The Solr ref guide does not document single value only, in fact it encourages
using copyField to populate the "field" to use for suggestions, which in fact
requires multiValued=true. So we can either treat it as a code bug and backport
this issue, or add a patch which adds a warning or exception when attempting to
use multiVal, or treat it as a documentation bug and add a note in refguide
amendments page for 4.10.x. I'm happy with any of these, my customer who got
bit by this can run a patched version if need be.
> 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: 4.10.4, 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
