[
https://issues.apache.org/jira/browse/SOLR-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915828#action_12915828
]
Ryan McKinley commented on SOLR-2134:
-------------------------------------
Is it worth the added complexity and potential performance hit to fudge the
behavior for the edge case?
As long as things don't crash with NaN, I'm not sure if worrying about NaN vs
Infinity sorting is worth it.
I don't really care though.
bq. as it has a defined order
I don't see anything in the javadocs -- are you just saying it is defined
because it is the same as what your JVM will do? Conceptually I guess NaN is
closer to zero then Infinity, but the other way round seems just as likely.
> Trie* fields should support sortMissingLast=true, and deprecate Sortable*
> Field Types
> -------------------------------------------------------------------------------------
>
> Key: SOLR-2134
> URL: https://issues.apache.org/jira/browse/SOLR-2134
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Reporter: Ryan McKinley
> Attachments: SOLR-2134-SortMissingLast.patch,
> SOLR-2134-SortMissingLast.patch, SOLR-2134-SortMissingLast.patch,
> SOLR-2134-SortMissingLast.patch
>
>
> With the changes in LUCENE-2649, the FieldCache also returns if the bit is
> valid or not. This is enough to support sortMissingLast=true with Trie*
> fields. Then we can get rid of the Sortable* fields
--
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]
