elasticsearch type_error ai_generated true

MapperParsingException: 解析 geo_shape 字段 [location] 失败 - 期望 [point] 但找到 [polygon]

MapperParsingException: failed to parse geo_shape field [location] - expected [point] but found [polygon]

ID: elasticsearch/geo-shape-indexing-error

其他格式: JSON · Markdown 中文 · English
87%修复率
88%置信度
1证据数
2023-09-05首次发现

版本兼容性

版本状态引入弃用备注
7.10.0 active — — —
7.17.0 active — — —
8.0.0 active — — —
8.7.0 active — — —

根因分析

索引映射将字段定义为点类型，但索引文档包含多边形或其他几何类型，导致解析不匹配。

English

The index mapping defines the field as a point type, but the indexed document contains a polygon or other geometry type, causing a parsing mismatch.

generic

官方文档

https://www.elastic.co/guide/en/elasticsearch/reference/current/geo-shape.html

解决方案

  1. Update the mapping to accept multiple geometry types by setting `'ignore_malformed': true` for the field: PUT my_index/_mapping { "properties": { "location": { "type": "geo_shape", "ignore_malformed": true } } }
  2. Change the mapping to the correct geometry type (e.g., polygon) and reindex: PUT my_index/_mapping { "properties": { "location": { "type": "geo_shape", "orientation": "right" } } }
  3. Use a pipeline to transform the geometry before indexing: PUT _ingest/pipeline/geo_transform { "processors": [ { "geo_shape": { "field": "location", "target_field": "location", "shape_type": "polygon" } } ] }

无效尝试

常见但无效的做法:

  1. 50% 失败

    The mapping must explicitly define the geometry type (e.g., 'point', 'polygon') for validation. Omitting it can lead to unexpected behavior or performance issues.

  2. 30% 失败

    This loses spatial precision and may not be acceptable for queries that require exact geometry. It also requires code changes.

  3. 60% 失败

    This is disruptive to production and may cause data loss if not backed up. It also doesn't fix the immediate indexing error.