CONTENT TYPE field do not support searching – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.6-7.1

Briefly, this error occurs when you try to search a field in Elasticsearch that is not indexed or not searchable. This is common with fields that have the “enabled” property set to false or the “index” property set to “no”. To resolve this issue, you can either change the mapping of the field to make it searchable by setting “index” to “true” or “enabled” to “true”, or you can search a different field that is searchable. Please note that changing the mapping requires reindexing the data.

This guide will help you check for common problems that cause the log ” [” + CONTENT_TYPE + “] field do not support searching; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[” + CONTENT_TYPE + “] field do not support searching; ” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  @Override
 public Query termQuery(Object value; QueryShardContext context) {
 throw new QueryShardException(context; "[" + CONTENT_TYPE + "] field do not support searching; " +
 "use dedicated aggregations instead: ["
 + name() + "]");