lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nabble (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-1877) Use NativeFSLockFactory as default for new API (direct ctors & FSDir.open)
Date Sat, 10 Sep 2011 23:35:10 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102178#comment-13102178
] 

Nabble commented on LUCENE-1877:
--------------------------------

Dear JIRA jira@apache.org,

Please fix the embedding code of your Nabble application "[jira] Commented: (LUCENE-1877)
Use NativeFSLockFactory as default for new API (direct ctors & FSDir.open)" as soon as
possible because Nabble will stop supporting that code in a few days. Here is the code you
should use in your HTML page:

<a id="nabblelink" href="http://lucene.472066.n3.nabble.com/jira-Created-LUCENE-1877-Improve-IndexWriter-javadoc-on-locking-tp574303p574326.html">[jira]
Commented: (LUCENE-1877) Use NativeFSLockFactory as default for new API (direct ctors &
FSDir.open)</a>
<script src="http://http://lucene.472066.n3.nabble.com/embed/f574326"></script>

Here is the link to your application:
http://lucene.472066.n3.nabble.com/jira-Created-LUCENE-1877-Improve-IndexWriter-javadoc-on-locking-tp574303p574326.html

If you don't update your HTML page, the embedded application will stop working. Note that
we won't send more emails about this issue and we apologize for the inconvenience.

Sincerely,
The Nabble team



> 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: general/javadocs
>            Reporter: Mark Miller
>            Assignee: Uwe Schindler
>             Fix For: 2.9
>
>         Attachments: LUCENE-1877.patch, 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}  <p>Opening an <code>IndexWriter</code> creates a lock file
for the directory in use. Trying to open
>   another <code>IndexWriter</code> 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.</p>{code}
> Anyone remember why NativeFSLockFactory is not the default over SimpleFSLockFactory?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message