[
https://issues.apache.org/jira/browse/SOLR-10114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864038#comment-15864038
]
Yonik Seeley commented on SOLR-10114:
-------------------------------------
bq. if the fix is to store the version with the child docs, it requires
reindexing to resolve the issue.
Right, this won't fix old indexes.
bq. I was thinking of adding another iteration to fetch parent version for
childdocs without version.
That seems difficult, unless we just assume that any doc w/o a version is a
child doc.
Also, another thing to watch out for is that the version field is technically
not mandatory for non-solrcloud. The presence of a \_root\_ field could be
used to further determine if a doc is a child doc, but that may be expensive
too.
> child documents lack _version_, susceptible to reordered delete-by-query
> -------------------------------------------------------------------------
>
> Key: SOLR-10114
> URL: https://issues.apache.org/jira/browse/SOLR-10114
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Yonik Seeley
>
> It looks like when a block of documents is indexed, child documents get no
> \_version\_ field. This means (among other potential issues) that a
> delete-by-query that is reordered will cause matching child documents to be
> deleted. DBQ normally prevents deleting newer docs by including a
> restriction on \_version\_, which doesn't work for anything lacking that
> field. Re-ordered delete-by-term of any child docs would also be affected
> (although it should be a much rarer issue.)
> The leading candidate for a fix is to use the exact same \_version\_ for all
> child docs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
