On 7/2/2018 9:18 AM, jeebix wrote: > I don't understand why for example "type_cmd_s" get the field type attribute > "singleValued", but "TTC" or "kits_sans_suite" get "multiValued" attribute ? > Why those field are in the managed-schema and enseigne_s (for example) is > not ?
The field named enseigne_s is almost certainly handled by a dynamic field definition, most likely one with the name "*_s". That field (and its field type) do not have multiValued="true". This was probably already in your schema before you did any indexing. The ones that were automatically added by the data-driven nature of your schema were added as the "strings" type, which IS multi-valued. The update processor definition that is in the Solr examples is set up to add fields as multiValued, so that if a later indexing request comes in with multiple values for the field, it will not fail. This is the major danger of relying on Solr to automatically add fields to your schema. Chances are good that the choice it makes for the field will be the wrong choice. And when that happens, you will need to fix the schema and completely reindex. https://wiki.apache.org/solr/HowToReindex Thanks, Shawn
