[
https://issues.apache.org/jira/browse/SOLR-10114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870353#comment-15870353
]
ASF subversion and git services commented on SOLR-10114:
--------------------------------------------------------
Commit d49edabf8992c2b2f9e2583e289cc58a4e71fd31 in lucene-solr's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d49edab ]
SOLR-10114: test cleanup
> 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.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]
