[
https://issues.apache.org/jira/browse/SOLR-9004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244491#comment-15244491
]
ASF GitHub Bot commented on SOLR-9004:
--------------------------------------
GitHub user arafalov opened a pull request:
https://github.com/apache/lucene-solr/pull/30
Ensure text field is not multiValued (SOLR-9004)
Fix the field definition to match the README descriptions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/arafalov/lucene-solr-1 patch-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/lucene-solr/pull/30.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #30
----
commit c27a4477a563123587ddb51753df44af7df58f9b
Author: Alexandre Rafalovitch <[email protected]>
Date: 2016-04-17T00:47:50Z
Ensure text field is not multiValued
Fix the field definition to match the README descriptions.
----
> 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
> Priority: Minor
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
