lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <>
Subject [jira] Commented: (LUCENE-690) LazyField use of IndexInput not thread safe
Date Thu, 19 Oct 2006 19:01:36 GMT
    [ ] 
Grant Ingersoll commented on LUCENE-690:

Comment from Hoss, which I think should be on the issue:

: Otherwise, my understanding is that the seek() call before reading
: should put it into a known state, but I am guessing your not so sure on
: that point.  So the question is seek() sufficient to put an IndexInput
: into a known safe state, right?

isn't it more subtle then that? ... IndexInput.clone() states that the
clone will be "positioned at the same point as the stream they were cloned
from" ... that implies that the clone will be in a consistent usable state
even with the client calling seek on the clone() .... is that
invarient currently met by BufferedIndexInput in a multithreaded case?


> LazyField use of IndexInput not thread safe
> -------------------------------------------
>                 Key: LUCENE-690
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 2.0.1
>            Reporter: Yonik Seeley
> Hypothetical problem: IndexInput.clone() of an active IndexInput could result in a corrupt
> LazyField clones the FieldsReader.fieldsStream, which could be in use via IndexReader.document()

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message