Could not parse inline template – How to solve this Elasticsearch error

Average Read Time

2 Mins

Could not parse inline template – 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Could not parse inline template ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: template and mustache.

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 “Could not parse inline template”classname  is SearchTemplateRequest.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (parser.currentToken() == XContentParser.Token.START_OBJECT) {
 //convert the template to json which is the only supported XContentType (see CustomMustacheFactory#createEncoder)
 try (XContentBuilder builder = XContentFactory.jsonBuilder()) {
 request.setScript(Strings.toString(builder.copyCurrentStructure(parser)));
 } catch (IOException e) {
 throw new ParsingException(parser.getTokenLocation(); "Could not parse inline template"; e);
 }
 } else {
 request.setScript(parser.text());
 }
 }; SOURCE_FIELD; ObjectParser.ValueType.OBJECT_OR_STRING);

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content