[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lucene-user
Subject:    Re: Directory, IndexInput and IndexOutput concurrency
From:       Uwe Schindler <uwe () thetaphi ! de>
Date:       2012-05-30 5:24:14
Message-ID: 2d8348f2-cbde-4f64-b18f-ffbe96cb6e17 () email ! android ! com
[Download RAW message or body]


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 <lucene@mikemccandless.com> schrieb:

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 <dhruv21@gmail.com> wrote:
> 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 use thread confinement? Are there any other OS level
> file system guarantees which the Lucene's Directory implementations make
> use of and which I should ensure from my in-memory implementation?
>
> I am using Lucene 3.0.3 and I have looked at RAMDirectory's and
> RAMIndexInputStream and RAMIndexOutputStream code but it does not
> explicitly mention any concurrency requirements.
>
> Any help in this regard will be appreciated.
>
> Thank you,
> -Dhruv

_____________________________________________

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



[prev in list] [next in list] [prev in thread] [next in thread]