On 9/8/2021 8:05 AM, HariBabu kuruva wrote:
I have checked with the DEV team regarding multivalue error. They say that :
the fields which require/have multiple values were already set to
multivalued=true . For non-multi valued fields also we are getting multiple
values. That is the problem.
Are you using the atomic update feature? There are very specific schema
requirements for Atomic Update. If you're not using Atomic Update, then
you can ignore this whole message. From the ref guide:
-------
The core functionality of atomically updating a document requires that
all fields in your schema must be configured as stored (stored="true")
or docValues (docValues="true") except for fields which are <copyField/>
destinations, which must be configured as stored="false". Atomic updates
are applied to the document represented by the existing stored field
values. All data in copyField destinations fields must originate from
ONLY copyField sources.
If <copyField/> destinations are configured as stored, then Solr will
attempt to index both the current value of the field as well as an
additional copy from any source fields. If such fields contain some
information that comes from the indexing program and some information
that comes from copyField, then the information which originally came
from the indexing program will be lost when an atomic update is made.
There are other kinds of derived fields that must also be set so they
aren't stored. Some spatial field types, such as BBoxField and
LatLonType, use derived fields. CurrencyFieldType also uses derived
fields. These types create additional fields which are normally
specified by a dynamic field definition. That dynamic field definition
must be not stored, or indexing will fail.
-------
That requires a little bit of an update -- definitions that must be
unstored must also have docValues set to false.
If copyField is in use and destinations are stored, that could lead to
multiple values when using atomic update.
Thanks,
Shawn
