Field is of type but only numeric types are supported – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when a non-numeric field is being used in a context where only numeric fields are supported, such as in a mathematical operation or a specific type of aggregation. To resolve this issue, you can either change the field type to a numeric type if it’s appropriate, or modify your query to only include numeric fields. If the field contains numeric data but is not mapped as a numeric type, you may need to reindex your data with the correct mapping.

This guide will help you check for common problems that cause the log ” field [{}] is of type [{}]; but only numeric types are supported. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, query.

Log Context

Log “field [{}] is of type [{}]; but only numeric types are supported.” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (fieldType instanceof GeoPointFieldType) {
 return parseGeoVariable(parser; context; fieldType; mode);
 } else if (fieldType instanceof NumberFieldMapper.NumberFieldType) {
 return parseNumberVariable(parser; context; fieldType; mode);
 } else {
 throw new ParsingException(parser.getTokenLocation(); "field [{}] is of type [{}]; but only numeric types are supported.";
 fieldName; fieldType);
 }  private AbstractDistanceScoreFunction parseNumberVariable(XContentParser parser; SearchExecutionContext context;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?