On 10/27/22 15:51, Thomas Corthals wrote:
I can reproduce it on a pristine techproducts example index by unpacking
the Solr 9.0.0 download and changing the schema in the sample configset
*before* I even start that Solr instance for the very first time. That
should rule out a conflict between the existing index and the schema as the
index was built from scratch with that schema and I didn't change it
afterwards.
The error only occurs with _nest_path_ in the schema, changing _root_ to
stored="true" alone doesn't cause it.
The error still only occurs with a commit between the initial "add" of the
doc and the atomic update. The error doesn't occur if I commit after both
"add"'s.
Odd.
I have no idea what "_nest_path_" even does. I have never actually used
the nested documents feature. I am basing all this on things I have
read, not actual experience.
My best guess about this is that it is throwing an exception because it
detects that you have split the parent and child doc into different
segments. If you update something for a parent or child document, you
will need to update or reindex EVERY document that is connected to
either the child or its parent, and it will need to be done without
interleaved commits. Ideally, all of those documents will be in the
same indexing batch.
I think it is entirely possible that Solr 8 does not detect a problem,
so it allows the indexing, where Solr 9 does detect it. If that's it, it
REALLY sucks that the detection results in that particular exception,
because that would mean that the exception has nothing to do with the
actual problem.
Thanks,
Shawn
