: expected (at ) but found – Elasticsearch Error How To Solve Related Issues



: expected (at ) but found – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 

 

This guide will help you check for common problems that cause the log “: expected (at ) but found” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”: expected [{}] (at [{}]) but found [{}]”classname  is Intervals.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// char token
  if (token.ch != 0) {
  char found = string.charAt(startToken);
  if (found != token.ch) {
  throw new ParsingException(source; invalidIntervalMessage(string) + ": expected [{}] (at [{}]) but found [{}]";
  token.ch; startToken; found);
  }
  startToken++;
  }
  // number char

 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 malformed query, expected END_OBJECT but found FIELD_NAME error in Kibana (Elastic Search) -views 29,557 ,score 14

BULK API : Malformed action/metadata line [3], expected START_OBJECT but found [VALUE_STRING] -views   11,127,score 10

 

 

About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now