[
https://issues.apache.org/jira/browse/SOLR-10238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley closed SOLR-10238.
-------------------------------
Resolution: Won't Fix
Marking as won't-fix. We can outright remove this and other spatial fields I
deprecated today in the future for 8.0.
RE example: I was kinda hoping [~arafalov] would (eventually) massively slim
down our example configs to not even have what aren't being demonstrated in the
sample in question. But we needn't wait for that.
> Remove LatLonType in 7.0; replaced by LatLonPointSpatialField
> -------------------------------------------------------------
>
> Key: SOLR-10238
> URL: https://issues.apache.org/jira/browse/SOLR-10238
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: spatial
> Reporter: David Smiley
> Assignee: David Smiley
> Fix For: master (7.0)
>
>
> LatLonPointSpatialField is about to land in SOLR-10039. This field is
> superior to LatLonType. In 7.0, lets remove LatLonType and mark it
> deprecated in 6.x? Or must this wait yet another release cycle?
> FYI RPT fields still have life in them due to their ability to index
> non-point shapes, handle custom (user coded ) shapes, and heatmaps, and are
> not limited to a lat-lon coordinate space.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
