and must be set for geo fields. – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” and must be set for geo fields. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: query and index.

Log Context

Log “[{}] and [{}] must be set for geo fields.”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else {
 throw new ElasticsearchParseException("parameter [{}] not supported!"; parameterName);
 if (origin == null || scaleString == null) {
 throw new ElasticsearchParseException("[{}] and [{}] must be set for geo fields."; DecayFunctionBuilder.ORIGIN;
 double scale = DistanceUnit.DEFAULT.parse(scaleString; DistanceUnit.DEFAULT);
 double offset = DistanceUnit.DEFAULT.parse(offsetString; DistanceUnit.DEFAULT);
 IndexGeoPointFieldData indexFieldData = context.getForField(fieldType);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content