[
https://issues.apache.org/jira/browse/SOLR-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438379#comment-16438379
]
David Smiley commented on SOLR-11731:
-------------------------------------
Sorry I had run one test a bunch of times but forgot about the whole suite,
thus Jenkins failed. As explained in the commit message, we're back at 7
decimal places now so that we can retain the desirable property that a number
provided with <= 7 decimal places will round-trip (i.e. will be returned in the
same precision as given). For example, this keeps 40 as-such instead of
39.99999997. This is accurate to ~1.37 cm or so. The theoretical 1.04cm is
still possible in terms of the underlying sorting and if you gave the data in
that level of accuracy (8 decimal places or more) being accurate to that but
when retrieved it's only to 1.37cm accuracy.
> 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
