DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-20 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-20 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-20 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-20 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-20 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-20 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-22 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-22 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-06-25 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-06-25 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-22 Thread Otis Gospodnetic
I didn't follow this closely, but are you saying that LuceneIndexAccessor then replaces IOError caused by locking with blocking calls? It sounds like the client of LuceneIndexAccessor still needs to keep track of open IndexReaders, IndexWriters, etc., or else one can end up with a hard-to-track bl

Re: DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-22 Thread Maik Schreiber
> I didn't follow this closely, but are you saying that > LuceneIndexAccessor then replaces IOError caused by locking with > blocking calls? It sounds like the client of LuceneIndexAccessor still > needs to keep track of open IndexReaders, IndexWriters, etc., or else > one can end up with a hard-t

Re: DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-22 Thread Otis Gospodnetic
Hi Maik, So what happens in this case: IndexAccessProvider accessProvider = new IndexAccessProvider(directory, analyzer); LuceneIndexAccessor accessor = new LuceneIndexAccessor(accessProvider); accessor.open(); IndexWriter writer = accessor.getWriter(); // reference to the same

Re: DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-22 Thread Maik Schreiber
> IndexWriter writer = accessor.getWriter(); > // reference to the same instance? > IndexWriter writer2 = accessor.getWriter(); > writer.addDocument(); > writer2.addDocument(); Yes, regardless of which thread invokes getWriter(). This means multiple threads are concurrently able to add new

Re: DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-22 Thread Daniel Naber
On Sunday 22 May 2005 21:01, Maik Schreiber wrote: > Yes, regardless of which thread invokes getWriter(). This means multiple > threads are concurrently able to add new documents. Isn't t that already possible without any accessor class (you need to use the same IndexWriter for all your threads)

Re: DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-22 Thread Maik Schreiber
> Isn't t that already possible without any accessor class (you need to use > the same IndexWriter for all your threads)? Yes, but you also need to keep track of who's using the writer before you can close it. Additionally, closing a writer yourself doesn't make sure that cached readers and searc

Re: DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-23 Thread Daniel Naber
On Sunday 22 May 2005 20:17, Otis Gospodnetic wrote: > To deal with managing index-modifying access to the index I often use > code that acts as a facade to IndexReader/Writer and provides methods > such as index(), optimize(), and delete().  All of these > methods have index-modifying cod

Re: DO NOT REPLY [Bug 34995] - Contribution: LuceneIndexAccessor

2005-05-25 Thread Otis Gospodnetic
What I described is really nothing more than a few methods like this: public void index(Indexable data) throws IOException { synchronized(_directory) { IndexWriter writer = getFSWriter(); try { Document doc = creat