[
https://issues.apache.org/jira/browse/LUCENE-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591716#comment-13591716
]
Robert Muir commented on LUCENE-3918:
-------------------------------------
{quote}
Also, it's not clear to me at the moment (but I admit I haven't thought about
it much) how can you sort documents during indexing, while the values to be
sorted by may still be unknown? I.e. what if your sort-by-key is a
NumericDocValues which the Codec hasn't seen yet? How should it write posting
lists, stored fields etc.? Does this mean the Codec must cache the entire
to-be-written segment in RAM? That will consume much more RAM than the approach
in this issue ...
{quote}
I totally agree with Shai.
If someone opened and issue to provide an option where IndexWriter constantly
optimized in the background, i would be totally against that. Same goes for it
doing sorting in the background: unless someone comes up with some serious
magic, i dont see this happening with acceptable runtime.
> Port index sorter to trunk APIs
> -------------------------------
>
> Key: LUCENE-3918
> URL: https://issues.apache.org/jira/browse/LUCENE-3918
> Project: Lucene - Core
> Issue Type: Task
> Components: modules/other
> Affects Versions: 4.0-ALPHA
> Reporter: Robert Muir
> Fix For: 4.2, 5.0
>
> Attachments: LUCENE-3918.patch, LUCENE-3918.patch, LUCENE-3918.patch,
> LUCENE-3918.patch, LUCENE-3918.patch
>
>
> LUCENE-2482 added an IndexSorter to 3.x, but we need to port this
> functionality to 4.0 apis.
--
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]
