[
https://issues.apache.org/jira/browse/LUCENE-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594614#comment-13594614
]
Shai Erera commented on LUCENE-4752:
------------------------------------
When I thought about AtomicReaderFactory I thought about something that returns
a single AtomicReader. IW-wise, that makes more sense (as an API) than
something that reorders a list of segments. Reordering can be left to things
like MergePolicy. In fact, I took a look at MP API, and maybe if we change
OneMerge from holding a {{List<SegmentReader>}} to {{List<AtomicReader>}}, we
could write an MP which sorts segments together by opening a
SortingAtomicReader over the segments that were picked for merge?
I think, if we do that, we don't need any hook on IWC
({{AtomicReaderFactory}}), although that might be useful in other cases, but
outside the scope of this issue. All we'll need is a SortingMP?
> Merge segments to sort them
> ---------------------------
>
> Key: LUCENE-4752
> URL: https://issues.apache.org/jira/browse/LUCENE-4752
> Project: Lucene - Core
> Issue Type: New Feature
> Components: core/index
> Reporter: David Smiley
> Assignee: Adrien Grand
>
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
