[
https://issues.apache.org/jira/browse/SOLR-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742905#comment-13742905
]
Robert Muir commented on SOLR-5170:
-----------------------------------
Err, that conversation is both wrong and totally irrelevant. Its based on some
bogus apples and oranges faceting benchmarks those guys did before: where they
spent lots of time optimizing that silly facet vint decode, whereas sortedset
is the simplest thing that can work and was done in like 2 days.
Ive said it before, I think its good to reinvestigate removing the BINARY type
completely. If i have to go optimize some loops somewhere in order to make that
happen, fine, its worth it to me to remove this useless shit.
I don't think you should refactor solr around broken assumptions and misleading
benchmarks.
> Spatial multi-value distance sort via DocValues
> -----------------------------------------------
>
> Key: SOLR-5170
> URL: https://issues.apache.org/jira/browse/SOLR-5170
> Project: Solr
> Issue Type: New Feature
> Components: spatial
> Reporter: David Smiley
> Assignee: David Smiley
> Attachments: SOLR-5170_spatial_multi-value_sort_via_docvalues.patch
>
>
> The attached patch implements spatial multi-value distance sorting. In other
> words, a document can have more than one point per field, and using a
> provided function query, it will return the distance to the closest point.
> The data goes into binary DocValues, and as-such it's pretty friendly to
> realtime search requirements, and it only uses 8 bytes per point.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
