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 ” Non-BKD field parameters are not supported for field type ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .
Log Context
Log “Non-BKD field parameters are not supported for [{}] field type”classname is LegacyGeoShapeFieldMapper.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :
public Builder(String name; Version version; boolean ignoreMalformedByDefault; boolean coerceByDefault) {
super(name);
if (ShapesAvailability.JTS_AVAILABLE == false || ShapesAvailability.SPATIAL4J_AVAILABLE == false) {
throw new ElasticsearchParseException("Non-BKD field parameters are not supported for [{}] field type"; CONTENT_TYPE);
}
this.indexCreatedVersion = version;
this.ignoreMalformed = ignoreMalformedParam(m -> builder(m).ignoreMalformed.get(); ignoreMalformedByDefault);
this.coerce = coerceParam(m -> builder(m).coerce.get(); coerceByDefault);
Find & fix Elasticsearch problems
