Both and must be set for numeric 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 Check-Up which can resolve issues that cause many errors.

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

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

} else {
 throw new ElasticsearchParseException("parameter [{}] not supported!"; parameterName);
 }
 }
 if (!scaleFound || !refFound) {
 throw new ElasticsearchParseException("both [{}] and [{}] must be set for numeric fields."; DecayFunctionBuilder.SCALE;
 DecayFunctionBuilder.ORIGIN);
 }
 IndexNumericFieldData numericFieldData = context.getForField(fieldType);
 return new NumericFieldDataScoreFunction(origin; scale; decay; offset; getDecayFunction(); numericFieldData; mode);
 }

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content