Unknown Similarity type value for field name – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch encounters an unknown similarity type for a specific field. The similarity type is used to define how Elasticsearch should score matching documents. If the type is not recognized, this error is thrown. To resolve this issue, you can either use a predefined similarity type like “BM25” or “classic”, or define your own custom similarity in the index settings. Make sure to use the correct syntax and spelling when specifying the similarity type.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Unknown Similarity type [” + value + “] for field [” + name + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “Unknown Similarity type [” + value + “] for field [” + name + “]” class name is TypeParsers.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (value == null) {
 return null;    // use default
 SimilarityProvider similarityProvider = parserContext.getSimilarity(value.toString());
 if (similarityProvider == null) {
 throw new MapperParsingException("Unknown Similarity type [" + value + "] for field [" + name + "]");
 return similarityProvider;


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?

Get expert answers on Elasticsearch/OpenSearch