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 18:14:36 GMT
    [ ] 
Grant Ingersoll commented on LUCENE-690:

Defnitely an issue for a closed IndexInput, but that has been discussed elsewhere and there
isn't really anything satisfying to say there other than it is undeclared what will happen
(although my tests on local Directories indicate that it is "safe" in a simple environment).

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?

If it doesn't, what would you suggest for a fix?  I suppose maybe you could clone it as you
create the LazyField (which would put it in right at the correct position and there would
be no need to seek, right)  This would save a little time at the tradeoff of memory, right?

> 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