Completion field type must be indexed – Elasticsearch Error How To Solve Related Issues



Completion field type must be indexed – 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 “Completion field type must be indexed” 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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”Completion field type must be indexed”classname  is CompletionFieldMapper.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 
  @Override
  public Builder index(boolean index) {
  if (index == false) {
  throw new MapperParsingException("Completion field type must be indexed");
  }
  return builder;
  }
  }

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 ElasticSearch completion suggester with Java API -views 9,257 ,score 3

NEST / Elastic Search Auto-Completion 'Field [suggest] is not a completion suggest field' -views   1,718



Find Configuration Errors

Analyze Now