[
https://issues.apache.org/jira/browse/SOLR-9004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336858#comment-15336858
]
ASF subversion and git services commented on SOLR-9004:
-------------------------------------------------------
Commit 13ed5de600408e13936174620fec6404156b1771 in lucene-solr's branch
refs/heads/branch_5_5 from [~steve_rowe]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=13ed5de ]
SOLR-9004: Add 5.5.2 CHANGES entry
> films example's name field is created multiValued despite FAQ
> -------------------------------------------------------------
>
> Key: SOLR-9004
> URL: https://issues.apache.org/jira/browse/SOLR-9004
> Project: Solr
> Issue Type: Bug
> Affects Versions: 6.0
> Reporter: Alexandre Rafalovitch
> Assignee: Varun Thacker
> Priority: Minor
> Fix For: 5.6, 6.0.1, 6.1, 5.5.2, master (7.0)
>
>
> In the README.txt for the *films* example, it says:
> bq. Without overriding those field types, the _name_ field would have been
> guessed as a multi-valued string field type .... it makes more sense with this
> particular data set domain to have the movie name be a single valued
> general full-text searchable field,
> However, the actual Schema API call does not specify multiValued=false, just
> that it is of *text_general* type. That type is defined as multiValued, so
> the end result is multiValued as well, opposite to the explanation given.
--
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
