Field ” + currentFieldName + ” is a metadata field and cannot be added inside – Elasticsearch Error How To Solve Related Issues


Field ” + currentFieldName + ” is a metadata field and cannot be added inside – Elasticsearch Error How To Solve Related Issues

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 ” Field ” + currentFieldName + ” is a metadata field and cannot be added inside ” 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: metadata and index.

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”Field [” + currentFieldName + “] is a metadata field and cannot be added inside”classname  is DocumentParser.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

while (token != XContentParser.Token.END_OBJECT) {
  if (token == XContentParser.Token.FIELD_NAME) {
  currentFieldName = parser.currentName();
  paths = splitAndValidatePath(currentFieldName);
  if (context.mapperService().isMetadataField(context.path().pathAsText(currentFieldName))) {
  throw new MapperParsingException("Field [" + currentFieldName + "] is a metadata field and cannot be added inside"
  + " a document. Use the index API request parameters.");
  } else if (containsDisabledObjectMapper(mapper; paths)) {
  parser.nextToken();
  parser.skipChildren();
  }

 

Optimize Elasticsearch Performance

Try The Tool