[ https://issues.apache.org/jira/browse/LUCENE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750632#action_12750632 ] Uwe Schindler edited comment on LUCENE-1877 at 9/2/09 12:53 PM: ---------------------------------------------------------------- Final patch. I implemented additional: - all FS-based lock factories use the same prefix encoding. They are now (mostly) compatible. E.g. a lock obtained with NativeFSLockFactory would also be seen as locked with SimpleFSLockFactory. - Added LockFactory ctors with no param. The FSDir will set the lockdir to itsself in this case. - Added test for LUCENE-1885 - Added note about deprecation of all FSDir related system properties, fixed some docs Please test this extensively! I hope, I found all problems. was (Author: thetaphi): Final patch. I implemented additional: - all FS-based lock factories use the same prefix encoding. They are now (mostly) compatible. E.g. a lock obtained with NativeFSLockFactory would also be seen as locked with SimpleFSLockFactory. - Added LockFactory ctors with no param. The FSDir will set the lockdir to itsself in this case. - Added test for LUCENE-1885 Please test this extensively! I hope, I found all problems. > 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.

{code} > Anyone remember why NativeFSLockFactory is not the default over SimpleFSLockFactory? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org