Does not support DISTINCT yet it was specified – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.12-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when a DISTINCT clause is used in a query. Elasticsearch does not support the DISTINCT keyword as it is not a relational database. To resolve this issue, you can use the “terms” aggregation to get distinct values. Alternatively, you can use the “cardinality” aggregation to get the count of distinct values. Another option is to use a script to remove duplicates from the results. Remember to always check the syntax and structure of your queries to ensure they are compatible with Elasticsearch.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” does not support DISTINCT yet it was specified ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “does not support DISTINCT yet it was specified” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 T build(Source source; Expression expression; DataType dataType);
 }  private static void forbidDistinct(Source source; Boolean distinct) {
 if (distinct != null) {
 throw new ParsingException(source; "does not support DISTINCT yet it was specified");


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?