New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solr config refers to deprecated LatLonType #1370
Comments
Shall we just remove it? It seems like it won't hurt existing adopters (who will have generated from the old template), and will improve matters for new users. |
no-reply
pushed a commit
that referenced
this issue
Jan 23, 2019
This type is deprecated in Solr. Its removal from the template here shouldn't affect existing adopters who may be using it. It will be removed only for folks running the generator after this commit. Fixes #1370
bess
pushed a commit
that referenced
this issue
Apr 3, 2019
This type is deprecated in Solr. Its removal from the template here shouldn't affect existing adopters who may be using it. It will be removed only for folks running the generator after this commit. Fixes #1370
bess
pushed a commit
that referenced
this issue
Apr 3, 2019
This type is deprecated in Solr. Its removal from the template here shouldn't affect existing adopters who may be using it. It will be removed only for folks running the generator after this commit. Fixes #1370
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't think we're using this anywhere. Can we drop this field type or do we want to migrate to one of:
LatLonPointSpatialField
,SpatialRecursivePrefixTreeField
, orRptWithGeometrySpatialField
?The text was updated successfully, but these errors were encountered: