[
https://issues.apache.org/jira/browse/SOLR-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley resolved SOLR-11731.
---------------------------------
Resolution: Fixed
Fix Version/s: 7.4
While debugging I checked that RetrieveFieldsOptimizer is smart enough to
recognize that a document can avoid being retrieved if LLPSF is listed (as long
as stored=false). I also observed that if LLPSF is stored, then Solr will
never automatically choose to get the docValue version (semantically
useDocValueAsStored is effectively always false for LLPSF). That's good since
there is precision loss.
Thanks again Karthik.
> LatLonPointSpatialField could be improved to return the lat/lon from docValues
> ------------------------------------------------------------------------------
>
> Key: SOLR-11731
> URL: https://issues.apache.org/jira/browse/SOLR-11731
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: spatial
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Minor
> Fix For: 7.4
>
> Attachments: SOLR-11731.patch, SOLR-11731.patch, SOLR-11731.patch
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> You can only return the lat & lon from a LatLonPointSpatialField if you set
> stored=true. But we could allow this (albeit at a small loss in precision)
> if stored=false and docValues=true.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
