Properties must be a map type – How to solve this Elasticsearch error

Average Read Time

2 Mins

Properties must be a map type – 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 ” properties must be a map type ” 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: 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”properties must be a map type”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return true;
  } else if (fieldName.equals("properties")) {
  if (fieldNode instanceof Collection && ((Collection) fieldNode).isEmpty()) {
  // nothing to do here; empty (to support "properties: []" case)
  } else if (!(fieldNode instanceof Map)) {
  throw new ElasticsearchParseException("properties must be a map type");
  } else {
  parseProperties(builder; (Map) fieldNode; parserContext);
  return true;
  } else if (fieldName.equals("include_in_all")) {


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

Analyze your cluster