You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alexandre Rafalovitch (JIRA)" <ji...@apache.org> on 2016/04/17 02:41:25 UTC
[jira] [Created] (SOLR-9004) films example's name field is created
multiValued despite FAQ
Alexandre Rafalovitch created SOLR-9004:
-------------------------------------------
Summary: 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org