[ https://issues.apache.org/jira/browse/SOLR-10114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mano Kovacs updated SOLR-10114: ------------------------------- Attachment: SOLR-10114.patch Adding patch with - fix by adding version for childdocs if there is - fix by using same insert-or-update logic when handling reordered DBQ - recovery and peersync tests. > 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 > Attachments: SOLR-10114.patch, SOLR-10114-validation.patch > > > 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