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 a radius parameter is not provided in a geospatial query in Elasticsearch. Elasticsearch requires a radius to perform geospatial queries. To resolve this issue, you should specify a radius in your query. This can be done by adding a “distance” parameter to your “geo_distance” filter or query. The value of the distance can be a string such as “12km” or a number representing meters. Also, ensure that the field you’re querying is correctly mapped as a geo_point or geo_shape data type.
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 ” radius is not specified ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .
Log Context
Log “radius is not specified” class name is GeoJson.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
} return switch (shapeType) {
case CIRCLE -> {
if (radius == null) {
throw new ElasticsearchParseException("radius is not specified");
}
verifyNulls(type; geometries; orientation; null);
Point point = coordinates.asPoint();
yield new Circle(point.getX(); point.getY(); point.getZ(); radius.convert(DistanceUnit.METERS).value);
}
