Hi Andreas, Atomic updates are defined within these conditions:
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 not, you lose your field content. Kind Regards, Furkan KAMACI On Mon, Apr 19, 2021 at 8:02 PM Andreas Hubold <[email protected]> wrote: > Hi seez, > > no, in my case, nested documents contained only fields as defined in the > schema. Actually, I didn't even use dynamic fields at all. It was just > the definition of the dynamic catch-all field that led to the problems. > It matched the name that was used to set nested documents. Because the > catch-all field was set to ignore unknown fields, Solr also ignored > nested documents in the code that performed the atomic update. Maybe > your problem has a different cause. > > Best, > Andreas > > seez wrote on 19.04.21 17:48: > > Andreas, > > > > Do your nested documents contain only dynamic fields? I am on 8.6.3 and I > > ran into this exact same issue. However in my case, even after disabling > > catch-all dynamic field, I still see the child documents getting deleted. > > > > > > > > > > > > -- > > Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html > > . > > >
