[
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-3.patch
Adding test fix
I went with namespacing, as monotonic counter would be a bigger change (added
jira for that SOLR-10151).
I changed the {{id:*}} to delete by id and by root, since the purpose of the
test was to validate that DBQ replayed version filter protects child-docs as
well.
Sorry for the inconvenience.
> Reordered delete-by-query can delete or omit child documents
> ------------------------------------------------------------
>
> 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)
> Affects Versions: 4.5
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Fix For: master (7.0)
>
> Attachments: SOLR-10114-2.patch, SOLR-10114-2.patch,
> SOLR-10114-3.patch, SOLR-10114.patch, SOLR-10114.patch,
> SOLR-10114-test-cleanup.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: [email protected]
For additional commands, e-mail: [email protected]
