[
https://issues.apache.org/jira/browse/LUCENE-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154620#comment-14154620
]
Robert Muir commented on LUCENE-5981:
-------------------------------------
My issue with that approach is that it will make a lot of tests harder to
debug. E.g. exception handling tests are calling this directly after getting
exception (without closing writer and potentially getting more exceptions).
> CheckIndex modifies index without write.lock
> --------------------------------------------
>
> Key: LUCENE-5981
> URL: https://issues.apache.org/jira/browse/LUCENE-5981
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Attachments: LUCENE-5981.patch
>
>
> Instead it asks you nicely to "not do that".
> Due to the way this is implemented, if you choose to drop corrupt segments,
> it should obtain the lock before actually doing any reads too, or it might
> lose more than you think or do other strange stuff.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
