[
https://issues.apache.org/jira/browse/LUCENE-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214605#comment-14214605
]
Tomás Fernández Löbbe commented on LUCENE-6060:
-----------------------------------------------
bq. in fact this can no longer happen with NativeFSLockFactory
What about {{SimpleFSLockFactory}}? That was the one that would have problems
in JVM crashes right? The Java bug linked in the javadoc is old and has been
fixed long ago, I guess that means that it's now safe and shouldn't leave a
write.lock file even if JVM crashes
> Remove IndexWriter.unLock
> -------------------------
>
> Key: LUCENE-6060
> URL: https://issues.apache.org/jira/browse/LUCENE-6060
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 4.10, 5.0, Trunk
>
> Attachments: LUCENE-6060.patch
>
>
> This method used to be necessary, when our locking impls were buggy, but it's
> a godawful dangerous method: it invites index corruption.
> I think we should remove it.
> Apps that for some scary reason really need it can do their own thing...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
