As Jan mentioned, I experienced the same problem on Solr 8.11. I can see in
your schema this commented out field:
Does removing the comment solve the issue? What about leaving that
commented out and also commenting out the _root_ field? In my case, either
including or excluding both fields seem
t_ field, so the thing you
> are seeing could very well be some bug related to atomic update.
> >>
> >> Can I propose that you create a minimal reproduction of this issue and
> upload somewhere?
> >> It could e.g. be a set of curl commands that, starting from a newly
The default managed_schema in solr 8.11 says:
On Thu, Dec 8, 2022 at 2:40 PM David Hastings
wrote:
> Interesting, this is kind of bizarre behavior.
> is:
>
> defaulted in the schema for 8.x?
>
> On Thu, Dec 8, 2022 at 9:31 AM Eduardo Gomez
&
> At first it wasn't clear to me what the problem you're having actually
> is. Then I glanced back at the message subject ... it is the only place
> you mention it.
Sorry Shawn, you are right, I didn't explain very clearly. So basically, in
Solr 8.11.1, I can see that updating an existing docume
Hi All,
I'm in the process of porting our Solr 7.5 to 8.11.1. I'm using our legacy
schema.xml with ClassicIndexSchemaFactory in solrconfig.xml.
I have seen there have been some changes introduced to how child docs are
updated (
https://solr.apache.org/guide/8_0/major-changes-in-solr-8.html#nested
