Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.
Briefly, this error occurs when you’re trying to index a document with a geo_point field in Elasticsearch, but the value of the field is not a POINT. Elasticsearch only supports POINT as a valid Well-Known Text (WKT) primitive for geo_point fields. To resolve this issue, ensure that the value of the geo_point field is a POINT. If you’re using a different WKT primitive, convert it to a POINT before indexing the document. Alternatively, consider using a geo_shape field if you need to index other types of geometric shapes.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
This guide will help you check for common problems that cause the log ” [geo_point] supports only POINT among WKT primitives; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .
Log Context
Log “[geo_point] supports only POINT among WKT primitives;” class name is GeoPoint.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
geometry = WellKnownText.fromWKT(GeographyValidator.instance(ignoreZValue); false; value);
} catch (Exception e) {
throw new ElasticsearchParseException("Invalid WKT format"; e);
}
if (geometry.type() != ShapeType.POINT) {
throw new ElasticsearchParseException("[geo_point] supports only POINT among WKT primitives; " +
"but found " + geometry.type());
}
Point point = (Point) geometry;
return reset(point.getY(); point.getX());
}
