Unexpected token ” + token + ” for order – How to solve this Elasticsearch error

Average Read Time

2 Mins

Unexpected token ” + token + ” for order – How to solve this Elasticsearch error

Opster Team

March-22, 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 ” Unexpected token ” + token + ” for order ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search, aggregations.

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 “Unexpected token [” + token + “] for [order]”classname  is InternalOrder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

orderAsc = false;
 } else {
 throw new ParsingException(parser.getTokenLocation(); "Unknown order direction [" + dir + "]");
 }
 } else {
 throw new ParsingException(parser.getTokenLocation(); "Unexpected token [" + token + "] for [order]");
 }
 }
 if (orderKey == null) {
 throw new ParsingException(parser.getTokenLocation(); "Must specify at least one field for [order]");
 }

 

Watch a demo of the Check-Up:

Analyze your cluster