You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by bu...@apache.org on 2004/11/06 01:11:07 UTC

DO NOT REPLY [Bug 32090] New: - org.apache.lucene.index.IndexReader and org.apache.lucene.index.IndexWriter cann't be used at the same time.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32090>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32090

org.apache.lucene.index.IndexReader and org.apache.lucene.index.IndexWriter cann't be used at the same time.

           Summary: org.apache.lucene.index.IndexReader and
                    org.apache.lucene.index.IndexWriter cann't be used at
                    the same time.
           Product: Lucene
           Version: 1.4
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Index
        AssignedTo: lucene-dev@jakarta.apache.org
        ReportedBy: xcchen@gmail.com


It will create Lock error exception, which sounds some sense.

But as a lucene plug-in into application server environment, user likes to leave
the IndexWriter and IndexReader be persistent as being created at server startup
 stage, because it seems that first operation on instance of either reader or
writer is pretty expensive [around 1 second on my machine], but the following
ones  are super fast, aorund 5 millisecond or so.

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