[
https://issues.apache.org/jira/browse/SOLR-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812238#comment-15812238
]
ASF subversion and git services commented on SOLR-9934:
-------------------------------------------------------
Commit 1d7379b680062eca766f0410e3db7ff9e9b34cb0 in lucene-solr's branch
refs/heads/master from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=1d7379b ]
SOLR-9934: SolrTestCase.clearIndex has been improved to take advantage of low
level test specific logic that clears the index metadata more completely then a
normal *:* DBQ can due to update versioning
> SolrTestCase.clearIndex should ensure IndexWriter.deleteAll is called
> ---------------------------------------------------------------------
>
> Key: SOLR-9934
> URL: https://issues.apache.org/jira/browse/SOLR-9934
> Project: Solr
> Issue Type: Test
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Assignee: Hoss Man
> Attachments: SOLR-9934.patch
>
>
> Normal deleteByQuery commands are subject to version constraint checks due to
> the possibility of out of order updates, but DUH2 has special support
> (triggered by {{version=-Long.MAX_VALUE}} for use by tests to override these
> version constraints and do a low level {{IndexWriter.deleteAll()}} call. A
> handful of tests override {{SolrTestCaseJ4.clearIndex()}} to take advantage
> of this (using copy/pasted impls), but given the intended purpose/usage of
> {{SolrTestCaseJ4.clearIndex()}}, it seems like the the base method in
> {{SolrTestCaseJ4}} should itself trigger this low level deletion, so tests
> get this behavior automatically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
