Skip to content
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

Refactor ignore_malformed and coerce options from geo_point field type to mapper #13285

Closed
nknize opened this issue Sep 2, 2015 · 0 comments · Fixed by #13289
Closed

Refactor ignore_malformed and coerce options from geo_point field type to mapper #13285

nknize opened this issue Sep 2, 2015 · 0 comments · Fixed by #13289
Labels
>enhancement :Search Foundations/Mapping Index mappings, including merging and defining field types Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch v2.0.0-beta2

Comments

@nknize
Copy link
Contributor

nknize commented Sep 2, 2015

The geo_point type ignore_malformed and coerce properties are currently part of the GeoPointField. This is inconsistent with other core types. This issue refactors these options from the GeoPointFieldMapper.GeoPointFieldType class to the GeoPointFieldMapper.Builder.

@nknize nknize added :Analytics/Geo Indexing, search aggregations of geo points and shapes :Search Foundations/Mapping Index mappings, including merging and defining field types v2.0.0 >enhancement labels Sep 2, 2015
@clintongormley clintongormley removed the :Analytics/Geo Indexing, search aggregations of geo points and shapes label Sep 6, 2015
@javanna javanna added the Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch label Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement :Search Foundations/Mapping Index mappings, including merging and defining field types Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch v2.0.0-beta2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants