[ 
https://issues.apache.org/jira/browse/LUCENE-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604148#comment-13604148
 ] 

Shai Erera commented on LUCENE-4752:
------------------------------------

Perhaps instead of telling us what we *can't* do, make suggestions on what we 
*can* do? You realize that we care about Lucene API at least as much as you do? 
And that if we propose to expose SegmentMerger it's not because we want to kill 
the project, but to allow flexibility (which has been expressed on the list few 
times) which eventually drives innovation and brings more progress to Lucene?

If you have a better idea, e.g. how can this be done with Codec, would you mind 
sharing with us? Nothing has been committed yet, we played with an idea, Adrien 
hacked it together ... that's it.

If there isn't a better (or any other) way to achieve that, then I think we 
should expose SegmentMerger. We shouldn't tell people "Lucene doesn't support 
online sorting of an index because we didn't want to expose super-expert API". 
That seems wrong to me. SegmentMerger can be marked @lucene.internal which 
gives you the freedom to do whatever you want with it. And given that all 
SortingSM will do is replace all ARs by a single SortingAR, I find it hard to 
see how overhauling (even rewriting from scratch) SM could possibly make that 
tiny hook SortingSM requires, a challenge.
                
> 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
>
>
> 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

Reply via email to