lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-9004) films example's name field is created multiValued despite FAQ
Date Mon, 09 May 2016 23:06:13 GMT

     [ https://issues.apache.org/jira/browse/SOLR-9004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hoss Man updated SOLR-9004:
---------------------------
    Fix Version/s:     (was: 6.0)
                   master (7.0)


Manually correcting fixVersion per Step #S5 of LUCENE-7271


> 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: 6.1, 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


Mime
View raw message