Failed to parse query. query is already defined. – 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 ” failed to parse query. query is already defined. ” 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 “failed to parse [{}] query. [query] is already defined.”classname  is FunctionScoreQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (token == XContentParser.Token.FIELD_NAME) {
 currentFieldName = parser.currentName();
 } else if (token == XContentParser.Token.START_OBJECT) {
 if (QUERY_FIELD.match(currentFieldName; parser.getDeprecationHandler())) {
 if (query != null) {
 throw new ParsingException(parser.getTokenLocation(); "failed to parse [{}] query. [query] is already defined.";
 NAME);
 }
 query = parseInnerQueryBuilder(parser);
 } else {
 if (singleFunctionFound) {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content