You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2016/03/25 14:48:25 UTC
[jira] [Created] (LUCENE-7141) OfflineSorter shouldn't always
forceMerge in the end
Michael McCandless created LUCENE-7141:
------------------------------------------
Summary: OfflineSorter shouldn't always forceMerge in the end
Key: LUCENE-7141
URL: https://issues.apache.org/jira/browse/LUCENE-7141
Project: Lucene - Core
Issue Type: Improvement
Reporter: Michael McCandless
Assignee: Michael McCandless
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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org