Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Message-ID: <5743179.200761290191533304.JavaMail.jira@thor>
Date: Fri, 19 Nov 2010 13:32:13 -0500 (EST)
From: "Uwe Schindler (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Subject: [jira] Resolved: (LUCENE-2770) Optimize SegmentMerger to work on
 atomic (Segment)Readers where possible
In-Reply-To: <22204682.197741290183313434.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/LUCENE-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Uwe Schindler resolved LUCENE-2770.
-----------------------------------

    Resolution: Fixed

Committed trunk revision: 1036970
Committed 3.x revision: 1036971

Thanks Mike for the help with the stupid bug because of not-cloned TVReader!

> Optimize SegmentMerger to work on atomic (Segment)Readers where possible
> ------------------------------------------------------------------------
>
>                 Key: LUCENE-2770
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2770
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Uwe Schindler
>            Assignee: Uwe Schindler
>            Priority: Minor
>             Fix For: 3.1, 4.0
>
>         Attachments: LUCENE-2770-3x.patch, LUCENE-2770-3x.patch, LUCENE-2770.patch, LUCENE-2770.patch, LUCENE-2770.patch
>
>
> This is a spin-off from LUCENE-2769:
> Currently SegmentMerger has some optimizations when it merges segments that are SegmentReaders (e.g. when doing normal indexing or optimizing). But when you do IndexWriter.addIndexes(IndexReader...) the listed IndexReaders may not really be per-segment. SegmentMerger should track down all passed in reads down to the lowest level (Segment)Reader (or other atomic readers like SlowMultiReaderWrapper) and then merge. We can then remove most MultiFields usage (except term merging itsself) and clean up the code.
> This especially saves lots of memory for merging norms, as no longer the duplicate norms arrays are created when MultiReaders are used!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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