Log Type starts with a .; it is recommended not to start a type name with a . – How To Solve Related Issues


Log Type starts with a .; it is recommended not to start a type name with a . – How To Solve Related Issues

Opster Team

Feb-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 ” Type starts with a .; it is recommended not to start a type name with a . ” 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 [{}] starts with a ‘.’; it is recommended not to start a type name with a ‘.'” classname is MapperService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         }
        if (typeNameStartsWithIllegalDot(mapper)) {
            if (Version.indexCreated(indexSettings).onOrAfter(Version.V_2_0_0_beta1)) {
                throw new IllegalArgumentException("mapping type name [" + mapper.type() + "] must not start with a '.'");
            } else {
                logger.warn("Type [{}] starts with a '.'; it is recommended not to start a type name with a '.'"; mapper.type());
            }
        }

        // 1. compute the merged DocumentMapper
        DocumentMapper oldMapper = mappers.get(mapper.type());




 

Optimize Elasticsearch Performance

Try The Tool