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 OpenSearch operation.
Briefly, this error occurs when you try to index a document with a geo_point field using a Well-Known Text (WKT) primitive other than POINT. OpenSearch only supports POINT for geo_point fields. To resolve this issue, you can either change the WKT primitive to POINT if it’s applicable, or consider using a geo_shape field type which supports various shapes like polygon, linestring etc. Also, ensure that your coordinates are correctly formatted and in the right order (longitude, latitude) for geo_point fields.
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; ” + “but found ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: .
Log Context
Log “[geo_point] supports only POINT among WKT primitives; ” + “but found ” class name is GeoPoint.java. We extracted the following from OpenSearch source code for those seeking an in-depth context :
geometry = new WellKnownText(false; new GeographyValidator(ignoreZValue)).fromWKT(value);
} catch (Exception e) {
throw new OpenSearchParseException("Invalid WKT format"; e);
}
if (geometry.type() != ShapeType.POINT) {
throw new OpenSearchParseException("[geo_point] supports only POINT among WKT primitives; " + "but found " + geometry.type());
}
Point point = (Point) geometry;
return reset(point.getY(); point.getX());
}
