[
https://issues.apache.org/jira/browse/LUCENE-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204986#comment-14204986
]
David Smiley commented on LUCENE-5702:
--------------------------------------
bq. What version are you using? It seems to be public in the latest release.
4.8.1. I see it's now public in 4.10, perhaps it was 4.9.
bq. Elasticsearch does something similar by allowing to sort eg. by the minimum
value of all documents contained in a given block, maybe there is some logic
you can reuse?
https://github.com/elasticsearch/elasticsearch/blob/1.4/src/main/java/org/elasticsearch/index/fielddata/fieldcomparator/LongValuesComparatorSource.java#L64
Thanks for the pointer. But my situation can't assume a given block and must
look in other segments. I realize it could be much faster if it looked within
the block but that would require re-indexing all documents in a parent-child
set when any change, and I'd rather not make that trade-off for this app.
bq. +1 to improve code reuse across comparators!
Ok, maybe I'll add something when I get time. Time... the ultimate luxury!
> Per-segment comparator API
> --------------------------
>
> Key: LUCENE-5702
> URL: https://issues.apache.org/jira/browse/LUCENE-5702
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Fix For: Trunk
>
> Attachments: LUCENE-5702.patch
>
>
> As a next step of LUCENE-5527, it would be nice to have per-segment
> comparators, and maybe even change the default behavior of our top*
> comparators so that they merge top hits in the end.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
