Re: Directory, IndexInput and IndexOutput concurrency

2012-05-29 Thread Uwe Schindler
In addition, IndexInput.clone must create abother view on the same file, useable from another thread. -- Uwe Schindler H.-H.-Meier-Allee 63, 28213 Bremen http://www.thetaphi.de Michael McCandless schrieb: Multiple threads are free to interact with Directory. But it will be only one thread at

Re: Directory, IndexInput and IndexOutput concurrency

2012-05-29 Thread Dhruv
Thank you Mike. This could be documented in Lucene's Directory and stream classes for others benefit too. On Tue, May 29, 2012 at 3:54 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > Multiple threads are free to interact with Directory. > > But it will be only one thread at a time in

Re: Directory, IndexInput and IndexOutput concurrency

2012-05-29 Thread Michael McCandless
Multiple threads are free to interact with Directory. But it will be only one thread at a time interacting with a single instance of IndexInput and IndexOutput. Mike McCandless http://blog.mikemccandless.com On Tue, May 29, 2012 at 6:39 PM, Dhruv wrote: > I am trying to implement an in-memory

Directory, IndexInput and IndexOutput concurrency

2012-05-29 Thread Dhruv
I am trying to implement an in-memory version of the Directory, IndexInput and IndexOutput classes, similar to RAMDirectory. Can someone please point out if there are any concurrency and thread safety requirements from these classes? Do the users of these classes implement client side locking or u