Murmur3 fields are not searchable name – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.1

Briefly, this error occurs when you try to search a field that is mapped with the Murmur3 hash function in Elasticsearch. Murmur3 is used for creating a hash of the field’s value, but it doesn’t support searching. To resolve this issue, you can either change the field’s mapping to a type that supports searching, or create a separate field specifically for searching. Another option is to use a script to convert the Murmur3 hash back to its original value during the search.

This guide will help you check for common problems that cause the log ” Murmur3 fields are not searchable: [” + name() + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins, index.

Log Context

Log “Murmur3 fields are not searchable: [” + name() + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return SourceValueFetcher.toString(name(); mapperService; format);
 }  @Override
 public Query termQuery(Object value; QueryShardContext context) {
 throw new QueryShardException(context; "Murmur3 fields are not searchable: [" + name() + "]");
 }  protected Murmur3FieldMapper(String simpleName;
 MappedFieldType mappedFieldType;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?