Specifying an attribute on the field type makes it the default for any field
of that type.
Setting multiValued=true on "ignored" simply allows it to be used for any
field, whether it is single or multi-valued, and any source data, whether it
has one or multiple values for that ignored field. Otherwise, you would get
an error if multiple values were given for an ignored field which had no
multiValued attribute, while the stated goal is to simply ignore the field
and its incoming values.
-- Jack Krupansky
-----Original Message-----
From: Alexandre Rafalovitch
Sent: Thursday, January 17, 2013 6:20 PM
To: solr-user@lucene.apache.org
Subject: What is the difference in defining multiValued on field and or
fieldtype?
Hello,
I was looking at the 'ignored' field in the example's schema.xml and
suddenly noticed that its field type has multiValued=true in the
definition. Wiki confirms that it is possible, but does not explains.
What's the difference between defining it on the type and on the field
itself? Because example has it defined on both.
I am confused suddenly, because we now have permutation of 9 different
values (true/false/missing ^ 2) and I am not sure what the exact semantics
is.
I am mostly interested in fieldType/@multiValued=true impact, but curious
about the other permutations.
Thanks,
Alex.
Personal blog: http://blog.outerthoughts.com/
LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch
- Time is the quality of nature that keeps events from happening all at
once. Lately, it doesn't seem to be working. (Anonymous - via GTD book)
