Ranges must contain objects but hit a – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch encounters a non-object type in the ‘ranges’ field, which is expected to contain only objects. This could be due to incorrect data types or malformed queries. To resolve this, ensure that the ‘ranges’ field contains only objects. Check your data types and query structure. Make sure that the data you’re trying to index matches the mapping you’ve defined. If you’re using a query, ensure that it’s correctly formatted and that the ‘ranges’ field is correctly populated with objects.

This guide will help you check for common problems that cause the log ” [ranges] must contain objects; but hit a ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search, aggregations.

Log Context

Log “[ranges] must contain objects; but hit a” class name is IpRangeAggregationBuilder.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 String from = null;
 String to = null;
 String mask = null;  if (parser.currentToken() != Token.START_OBJECT) {
 throw new ParsingException(parser.getTokenLocation(); "[ranges] must contain objects; but hit a " + parser.currentToken());
 while (parser.nextToken() != Token.END_OBJECT) {
 if (parser.currentToken() == Token.FIELD_NAME) {


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?