[ https://issues.apache.org/jira/browse/LUCENE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750650#action_12750650 ] Uwe Schindler commented on LUCENE-1877: --------------------------------------- bq. This is neat, but I don't think we should advertise it? Definitely not. b.q. Ie, it's unsupported to mix different LockFactory impls. EG, in this case, the reverse is not true, right? Exactly. > Use NativeFSLockFactory as default for new API (direct ctors & FSDir.open) > -------------------------------------------------------------------------- > > Key: LUCENE-1877 > URL: https://issues.apache.org/jira/browse/LUCENE-1877 > Project: Lucene - Java > Issue Type: Improvement > Components: Javadocs > Reporter: Mark Miller > Assignee: Uwe Schindler > Fix For: 2.9 > > Attachments: LUCENE-1877.patch, LUCENE-1877.patch, LUCENE-1877.patch > > > A user requested we add a note in IndexWriter alerting the availability of NativeFSLockFactory (allowing you to avoid retaining locks on abnormal jvm exit). Seems reasonable to me - we want users to be able to easily stumble upon this class. The below code looks like a good spot to add a note - could also improve whats there a bit - opening an IndexWriter does not necessarily create a lock file - that would depend on the LockFactory used. > {code}
Opening an IndexWriter
creates a lock file for the directory in use. Trying to open
> another IndexWriter
on the same directory will lead to a
> {@link LockObtainFailedException}. The {@link LockObtainFailedException}
> is also thrown if an IndexReader on the same directory is used to delete documents
> from the index.