Encountered more than one sort value for a – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.11-7.15

Briefly, this error occurs when Elasticsearch tries to sort a field that has multiple values. Elasticsearch can only sort on single-value fields. To resolve this, you can either change your data model to ensure the field you’re sorting on only has one value per document, or use a script to combine multiple field values into one for sorting purposes. Alternatively, you can use the max or min function to select a single value from the multiple values for sorting.

This guide will help you check for common problems that cause the log ” Encountered more than one sort value for a ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, sort, aggregations, search.

Log Context

Log “Encountered more than one sort value for a” class name is GeoLineBucketedSort.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 protected boolean advanceExact(int doc) throws IOException {
 if (docSortValues.advanceExact(doc)) {
 if (docSortValues.docValueCount() > 1) {
 throw new AggregationExecutionException("Encountered more than one sort value for a " +
 "single document. Use a script to combine multiple sort-values-per-doc into a single value.");
 }  // There should always be one weight if advanceExact lands us here; either
 // a real weight or a `missing` weight


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?