Type contains a it is recommended not to include it within a type name – How to solve related issues

Type contains a it is recommended not to include it within a type name – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you run 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 ” Type contains a it is recommended not to include it within a type name ” 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 “Type [{}] contains a ‘.’; it is recommended not to include it within a type name” classname is MapperService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             }
            if (mapper.type().contains(";")) {
                throw new InvalidTypeNameException("mapping type name [" + mapper.type() + "] should not include ';' in it");
            }
            if (mapper.type().contains(".") && !PercolatorService.TYPE_NAME.equals(mapper.type())) {
                logger.warn("Type [{}] contains a '.'; it is recommended not to include it within a type name"; mapper.type());
            }
            // we can add new field/object mappers while the old ones are there
            // since we get new instances of those; and when we remove; we remove
            // by instance equality
            DocumentMapper oldMapper = mappers.get(mapper.type());




 

Run the Check-Up to get customized recommendations like this:

checklist Run Check-Up

error

Heavy merges detected in specific nodes

error-img

Description

A large number of small shards can slow down searches and cause cluster instability. Some indices have shards that are too small…

error-img

Recommendations Based on your specific ES deployment you should…

Based on your specific ES deployment you should…

1

X-PUT curl -H [a customized code snippet to resolve the issue]

 

 

 

Optimize Elasticsearch Performance

Run The Tool