[
https://issues.apache.org/jira/browse/SOLR-5170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748324#comment-13748324
]
David Smiley commented on SOLR-5170:
------------------------------------
I'm slowly working on a benchmark using [Google
Caliper|http://code.google.com/p/caliper/]; but I have limited time on vacation
at the moment.
Bill: "it adds up" is not a memory concern, it's speed/performance overhead.
And your reference to geofilt and caching is largely irrelevant -- this is
about sorting. The "cache" in question (be it DocValues or whatever) is to put
all points in memory, it's *not* distance sorted results that may or may not be
likely to be re-used in another query.
> 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: [email protected]
For additional commands, e-mail: [email protected]
