[
https://issues.apache.org/jira/browse/LUCENE-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-4752:
---------------------------------
Attachment: LUCENE-4752.patch
bq. i think it would be way better to provide whatever 'hook' is needed for
this kinda stuff rather than allow subclassing of segmentmerger. like a proper
pluggable api (e.g. codec is an example of this) versus letting people just
subclass concrete things.
Here is a patch that allows for reordering via a simple hook instead of having
to subclass a class that does concrete things like SegmentMerger. The hook is
on MergePolicy because I felt like it makes sense to think about doc ID
reordering at merging time as part of a "merge policy" but it could also be put
somewhere else or have its own class. (The patch is just here to gather some
API feedback, I haven't tried to run anything with it yet). Does it look more
reasonable?
> 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
> Attachments: 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
