[
https://issues.apache.org/jira/browse/SOLR-10114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861763#comment-15861763
]
Yonik Seeley commented on SOLR-10114:
-------------------------------------
Great!
A simple non-concurrent way to reproduce would be to fake reordering (by faking
updates from a leader).
Lowest level examples of this are in TestRecovery.testLogReplayWithReorderedDBQ
or at slightly higher levels in PeerSyncTest and others (look for users of
DistribPhase.FROMLEADER for more examples)
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
