No index mapper found for field returning default doc values format – How to solve related issues

No index mapper found for field returning default doc values format – 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 ” No index mapper found for field returning default doc values format ” 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 and mapping.

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 “no index mapper found for field: [{}] returning default doc values format” classname is PerFieldMappingPostingFormatCodec.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
    
Override
    public DocValuesFormat getDocValuesFormatForField(String field) {
        final FieldMappers indexName = mapperService.indexName(field);
        if (indexName == null) {
            logger.warn("no index mapper found for field: [{}] returning default doc values format"; field);
            return defaultDocValuesFormat;
        }
        DocValuesFormatProvider docValuesFormat = indexName.mapper().docValuesFormatProvider();
        return docValuesFormat != null ? docValuesFormat.get() : defaultDocValuesFormat;
    }



 

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

Analyze your cluster