mirror of https://github.com/apache/lucene.git
LUCENE-1766: spell out IndexWriter's thread safety in the javadocs
git-svn-id: https://svn.apache.org/repos/asf/lucene/java/trunk@798835 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
e4585c507d
commit
8d5b662535
|
@ -186,6 +186,15 @@ import java.util.Map;
|
||||||
last commit. If you opened the writer with autoCommit
|
last commit. If you opened the writer with autoCommit
|
||||||
false you can also just call {@link #rollback()}
|
false you can also just call {@link #rollback()}
|
||||||
directly.</p>
|
directly.</p>
|
||||||
|
|
||||||
|
<a name="thread-safety"></a><p><b>NOTE</b>: {@link
|
||||||
|
<code>IndexWriter</code>} instances are completely thread
|
||||||
|
safe, meaning multiple threads can call any of its
|
||||||
|
methods, concurrently. If your application requires
|
||||||
|
external synchronization, you should <b>not</b> use the
|
||||||
|
<code>IndexWriter</code> instance for synchronization as
|
||||||
|
this can lead to deadlock. Use a private
|
||||||
|
<code>Object</code> instead. </p>
|
||||||
*/
|
*/
|
||||||
|
|
||||||
/*
|
/*
|
||||||
|
|
Loading…
Reference in New Issue