[
https://issues.apache.org/jira/browse/LUCENE-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666081#action_12666081
]
Hoss Man commented on LUCENE-1524:
----------------------------------
my take is similar to Michael...
The test in the patch doesn't seem valid to me. Specifying a reverse sort on
FIELD_1 just means that the documents must be returned in descending order of
the value in FIELD_1 -- it does not say anything about breaking ties when two
docs have equal values for FIELD_1, the behavior in that case is undefined (and
just so happens to be consistent)
> True reverse sorting
> --------------------
>
> Key: LUCENE-1524
> URL: https://issues.apache.org/jira/browse/LUCENE-1524
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.4
> Reporter: Jiri Kuhn
> Priority: Minor
> Fix For: 2.4.1
>
> Attachments: reverse.patch
>
>
> If documents sorted have the same sort value, they are sorted in the same way
> even if the reverse flag is true.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]