Type ” + type + ” cannot be used in multi 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 analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Type ” + type + ” cannot be used in multi field ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “Type [” + type + “] cannot be used in multi field”classname  is TypeParsers.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

throw new MapperParsingException("no type specified for property [" + multiFieldName + "]");
 if (type.equals(ObjectMapper.CONTENT_TYPE)
 || type.equals(ObjectMapper.NESTED_CONTENT_TYPE)
 || type.equals(FieldAliasMapper.CONTENT_TYPE)) {
 throw new MapperParsingException("Type [" + type + "] cannot be used in multi field");
 Mapper.TypeParser typeParser = parserContext.typeParser(type);
 if (typeParser == null) {
 throw new MapperParsingException("no handler for type [" + type + "] declared on field [" + multiFieldName + "]");


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content