Hello there, I’m having a strange issue with Solr after upgrading from 7.x to 8.11.1. I have a manually configured core using a schema.xml file. I’m defining my own uniqueKey field which is populated from my code. I rely on the uniqueKey behavior to properly handle updating documents in the core. Since the upgrade, this behavior has been lost and I’m seeing _root_ fields being generated in the core with values mirroring by uniqueKey id field, even though the _root_ field has not been defined in my schema.xml file. I can recreate the issue in the Solr UI by clearing the core, manually adding a document without a _root_ field via the Documents tab twice, then querying the core and seeing the duplication with _root_ fields in the result documents. All documentation that I can find is stating that the presence of a _root_ field makes the core treat documents in nested mode and breaks uniqueKey and deleteById functionality, which seems to be what I’m seeing. Is there any known solution for this issue?
I’m attaching a simplified version of the schema.xml in question for reference. Thank you, Jason LaFrance
schema.xml
Description: schema.xml
