[
https://issues.apache.org/jira/browse/LUCENE-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-3918:
---------------------------------
Attachment: LUCENE-3918.patch
bq. I use two parallel arrays to sort the documents (docs and values)
I updated the patch to use doc IDs as ords so that values are never swapped
(only doc IDs) and the numeric doc values don't need to be all loaded in memory.
bq. So one option is to remove the class, but still keep a test around which
does the addIndexes to make sure it works.
+1
bq. I don't want however to add a main that is limited to NumericDV ... and I
do think that stored fields / payload value are viable options.
I still don't get why someone would use stored fields rather than doc values
(either binary, sorted or numeric) to sort his index. I think it's important to
make users understand that stored fields are only useful to display results?
> 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-3918.patch, LUCENE-3918.patch,
> LUCENE-3918.patch, 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]
