Murmur3 fields are not searchable: ” + name() + ” – Elasticsearch Error How To Solve Related Issues



Murmur3 fields are not searchable: ” + name() + ” – 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 “Murmur3 fields are not searchable: ” + name() + “” 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: plugins, 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”Murmur3 fields are not searchable: [” + name() + “]”classname  is Murmur3FieldMapper.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return new DocValuesFieldExistsQuery(name());
  }
 
  @Override
  public Query termQuery(Object value; QueryShardContext context) {
  throw new QueryShardException(context; "Murmur3 fields are not searchable: [" + name() + "]");
  }
  }
 
  protected Murmur3FieldMapper(String simpleName; FieldType fieldType; MappedFieldType mappedFieldType;
  MultiFields multiFields; CopyTo copyTo) {







Find Configuration Errors

Try The Tool