Failed to parse query query is already defined – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when there is a duplication in the definition of a query in Elasticsearch. This could be due to a programming error or a misconfiguration. To resolve this issue, you should review your Elasticsearch query and ensure that each query is uniquely defined. You can also check your application’s code to ensure that it is not sending duplicate queries. Additionally, ensure that your Elasticsearch configuration does not have duplicate query definitions.

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: index, query.

Log Context

Log “failed to parse [{}] query. [query] is already defined.” class name is 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.";
 query = parseInnerQueryBuilder(parser);
 } else {
 if (singleFunctionFound) {


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?