Hi Jeremy, Based on the information you provided I would say that your price_list_url is recognized as an object instead of a field update. Depending on the way you update your document(s), this may succeed and do what you want, succeed and create flattened documents or fail. A flattened object would look like this in your case: { "id":"contracts 36F79718D0274 | 65 II I", " price_list_url.set":["https://prices.anywhere.com"], "_version_":1803386312791687168 }
How exactly are you updating your documents? What endpoint are you using and which request handler is processing your request? One potential root cause I can think of is mixing the endpoints /update/json/docs and /update. Sincerely, Christos On Sun, Jun 30, 2024 at 8:50 PM Jeremy Buckley - IQS-C <jeremy.buck...@gsa.gov.invalid> wrote: > After updating to 9.6.1, the following update is failing: > > [{ > "id":"contracts 36F79718D0274 | 65 II C", > "price_list_url" : { "set" : "https://prices.anywhere.com" } > }] > > Solr responds with: > > { > "responseHeader": { > "rf": 1, > "status": 400, > "QTime": 4 > }, > "error": { > "metadata": [ > "error-class", > "org.apache.solr.common.SolrException", > "root-error-class", > "org.apache.solr.common.SolrException" > ], > "msg": "Unable to index docs with children: the schema must include > definitions for both a uniqueKey field and the '_root_' field, using the > exact same fieldType", > "code": 400 > } > } > > We do not have nested child documents, at least not intentionally. Schema > has: > > <field name="id" type="string" indexed="true" multiValued="false" > omitNorms="true" omitPositions="true" omitTermFreqAndPositions="true" > stored="true" termVectors="false"/> > ... > <field name="price_list_url" type="string" indexed="true" stored="true" > multiValued="false" /> > ... > <uniqueKey>id</uniqueKey> > > There is no _root_ field defined in the schema, and it is > using ClassicIndexSchemaFactory. > We are running Solr Cloud, this collection has one shard and two replicas. > > Any ideas what could be causing this error or how to fix it? > > Thanks in advance! >