NonReserved can only contain tokens. Found nested rule: – How to solve this Elasticsearch error

NonReserved can only contain tokens. Found nested rule: – How to solve this Elasticsearch error

Opster Team

July-20, 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 that cause many errors.

This guide will help you check for common problems that cause the log ” nonReserved can only contain tokens. Found nested rule: ” 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: parser and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”nonReserved can only contain tokens. Found nested rule:”classname  is SqlParser.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

@Override
  public void exitNonReserved(SqlBaseParser.NonReservedContext context) {
  // tree cannot be modified during rule enter/exit _unless_ it's a terminal node
  if (!(context.getChild(0) instanceof TerminalNode)) {
  int rule = ((ParserRuleContext) context.getChild(0)).getRuleIndex();
  throw new ParsingException("nonReserved can only contain tokens. Found nested rule: " + ruleNames.get(rule));
  }
 
  // replace nonReserved words with IDENT tokens
  context.getParent().removeLastChild();

 

Run the Check-Up to get a customized report like this:

Analyze your cluster