Field ” + name() + ” of type ” + CONTENT_TYPE + ” – Elasticsearch Error How To Solve Related Issues

Field ” + name() + ” of type ” + CONTENT_TYPE + ” – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing many errors 


This guide will help you check for common problems that cause the log “field ” + name() + ” of type ” + CONTENT_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: plugin.

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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”field ” + name() + ” of type [” + CONTENT_TYPE + “]”classname  is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

  public Query existsQuery(QueryShardContext context) {
  if (hasDocValues()) {
  return new DocValuesFieldExistsQuery(name());
  } else {
  throw new QueryShardException(context; "field " + name() + " of type [" + CONTENT_TYPE + "] " +
  "has no doc values and cannot be searched");


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 No handler for type [string] declared on field [name] -views 43,711 ,score 104

Search by exact match in all fields in Elasticsearch -views   812,score 1



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now