lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4752) Merge segments to sort them
Date Mon, 18 Mar 2013 05:36:15 GMT


Shai Erera commented on LUCENE-4752:

bq. Why is the size of the class a concern?

Just to keep things readable. But it's not critical, however you prefer.

About OneMerge.readers and IW, not sure if you disagree with what I wrote? In the patch, IW
calls OneMerge.getMergeReaders to add them to SegmentMerger. It also does merge.readers.add()
and I propose to replace that call by merge.add(reader). So OneMerge.readers is not exposed
directly. Will that be a problem?
> Merge segments to sort them
> ---------------------------
>                 Key: LUCENE-4752
>                 URL:
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: core/index
>            Reporter: David Smiley
>            Assignee: Adrien Grand
>         Attachments: LUCENE-4752.patch, LUCENE-4752.patch, LUCENE-4752.patch, LUCENE-4752.patch
> It would be awesome if Lucene could write the documents out in a segment based on a configurable
order.  This of course applies to merging segments to. The benefit is increased locality on
disk of documents that are likely to be accessed together.  This often applies to documents
near each other in time, but also spatially.

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

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

View raw message