lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Updated] (LUCENE-7141) OfflineSorter shouldn't always forceMerge in the end
Date Fri, 25 Mar 2016 13:49:25 GMT


Michael McCandless updated LUCENE-7141:
    Attachment: LUCENE-7141.patch

First phase ... just a rote cutover to {{BytesRefIterator}}.

> OfflineSorter shouldn't always forceMerge in the end
> ----------------------------------------------------
>                 Key: LUCENE-7141
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>         Attachments: LUCENE-7141.patch
> Today it always does a final merge, to collapse all segments into a single segment.
> But typically the caller is going to re-iterate all values anyway, to go off and build
an FST or a BKD tree or something, and so that final forceMerge is often not necessary and
the merging can be done on the fly when the caller consumes the result.
> This is somewhat tricky to do ... I'd like to break it into steps, starting with fixing
the {{ByteSequencesReader}} API to implement {{BytesRefIterator}} instead of its own {{read(BytesRefBuilder)}}
method as a first step.

This message was sent by Atlassian JIRA

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

View raw message