lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrien Grand (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4858) Early termination with SortingMergePolicy
Date Tue, 09 Apr 2013 12:36:22 GMT


Adrien Grand commented on LUCENE-4858:

bq. The reason I did that is in case someone will want to sort by a stored field and numeric
field which have same names.

A Sorter which sorts by stored field values would indeed need to add more information to its
ID (at least to say that it is a stored field).

bq. "numericdv_field" is really unique, as you cannot have two numeric DV fields with the
same name, but different meaning.

Since doc values types are exclusive, could we then just say that these are doc values without
mentioning the type? I think this would help keep up with doc values types evolutions (for
example there used to be BYTES_FIXED_SORTED and BYTES_VAR_SORTED which have been merged into
SORTED) and/or additions (SORTED_SET). I would also prefer having something even more human-readable
(like "DocValues(fieldName=$fieldName,order=asc|desc)"?).

> Early termination with SortingMergePolicy
> -----------------------------------------
>                 Key: LUCENE-4858
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Adrien Grand
>            Assignee: Adrien Grand
>            Priority: Minor
>             Fix For: 4.3
>         Attachments: LUCENE-4858.patch, LUCENE-4858.patch, LUCENE-4858.patch, LUCENE-4858.patch,
LUCENE-4858.patch, LUCENE-4858.patch
> Spin-off of LUCENE-4752, see
> When an index is sorted per-segment, queries that sort according to the index sort order
could be early terminated.

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message