[jira] [Commented] (SOLR-9004) films example's name field is created multiValued despite FAQ

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-9004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336859#comment-15336859 ] 

ASF subversion and git services commented on SOLR-9004:
-------------------------------------------------------

Commit d216ce293b1f0d3ffb1af59797f1d001c49b8327 in lucene-solr's branch refs/heads/branch_5x from [~varunthacker]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d216ce2 ]

SOLR-9004: Fix name field type definition in films example


> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org