[
https://issues.apache.org/jira/browse/SOLR-10238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021592#comment-16021592
]
Hoss Man commented on SOLR-10238:
---------------------------------
bq. I think it would be too soon. AFAIK we try to keep index back compatibility
...
yeah, that's also my concern -- people who have built indexes with 6.x should
be able to use them in 7.0,which means keeping all the solr FieldType's around.
But we can/should certainly remove any mention of them from the master ref
guide and sample schema (looks like it's still mentioned in example/files and
example/example-DIH)
> 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]
