lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Updated] (LUCENE-3292) IOContext should be part of the SegmentReader cache key
Date Mon, 18 Jul 2011 10:57:00 GMT


Michael McCandless updated LUCENE-3292:

    Attachment: LUCENE-3292.patch

Attached patch, passing all tests. I think it's ready to commit.

This was trickier than I thought, because we had to take care to
ensure the deletions are applied only against readers pulled in a READ
context, and then pull the latest deletions from the READ context when
merging.  So I started with Varun's patch and iterated from there...

Also, there was a great simplification that fell out of this: we no
longer need that scary SR.loadTermsIndex method to load a terms index
after SR had already been created.  We only needed this for the case
where an SR opened for merging was then shared with an NRT reader, but
this is no longer possible.

> IOContext should be part of the SegmentReader cache key 
> --------------------------------------------------------
>                 Key: LUCENE-3292
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: core/index
>    Affects Versions: 4.0
>            Reporter: Simon Willnauer
>            Assignee: Varun Thacker
>            Priority: Minor
>             Fix For: 4.0
>         Attachments: LUCENE-3292.patch, LUCENE-3292.patch, LUCENE-3292.patch, LUCENE-3292.patch,
> Once IOContext (LUCENE-2793) is landed the IOContext should be part of the key used to
cache that reader in the pool

This message is automatically generated by JIRA.
For more information on JIRA, see:


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

View raw message