Error parsing document in field – How to solve this Elasticsearch error

Average Read Time

2 Mins

Error parsing document in field – 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 ” Error parsing document in field ” 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: plugins and document.

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”Error parsing document in field [{}]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

parsedContent = TikaImpl.parse(input; metadata; indexedChars);
  } catch (ZeroByteFileException e) {
  // tika 1.17 throws an exception when the InputStream has 0 bytes.
  // previously; it did not mind. This is here to preserve that behavior.
  } catch (Exception e) {
  throw new ElasticsearchParseException("Error parsing document in field [{}]"; e; field);
  if (properties.contains(Property.CONTENT) && Strings.hasLength(parsedContent)) {
  // somehow tika seems to append a newline at the end automatically; lets remove that again
  additionalFields.put(Property.CONTENT.toLowerCase(); parsedContent.trim());


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

Analyze your cluster