Query Changes
...
- Aggregating and sorting on _id is deprecated (7.6)
It’s possible to aggregate and sort on the built-in _id field by loading an expensive data structure called
fielddata. This was deprecated in 7.6 and will be disallowed by default in 8.0
Geo-Shape queries/mapping (7.7+)
- According to the 7.9 docs on geo-shape queries:
Requires the
geo_shapeMapping or thegeo_pointMapping.
- I don't think it'll apply to our mapping because we use geo-shape mapping type, which supports GEOJson (Multi)Point types (which we support now)
- Handle properly indexing rectangles that crosses the dateline #53810
- According to the 7.9 docs on geo-shape queries:
Mapping Changes
- Validation for dynamic templates (7.7)
So far misconfiguration of dynamic templates have been discovered when indexing a document with an unmapped field only. In Elasticsearch 8.0 and later versions, dynamic mappings have stricter validation, done at mapping update time. Invalid updates, such as using incorrect analyzer settings or unknown field types, fail. For indices created in Elasticsearch 7.7 and later version, the update succeeds but emits a warning.
- This may affect the mapping in
grqandmozart's ElasticSearch
...