Unrecognized enrich policy type – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.5-8.9

Briefly, this error occurs when Elasticsearch encounters an enrich policy type that it doesn’t recognize. This usually happens when you’re trying to create or update an enrich policy with a type that is not supported. To resolve this issue, ensure that you’re using a valid enrich policy type. The valid types are ‘exact_match’ and ‘geo_match’. Check your policy configuration and correct the type if it’s incorrect. If you’re using a custom enrich policy type, ensure it’s properly registered and recognized by Elasticsearch.

This guide will help you check for common problems that cause the log ” Unrecognized enrich policy type [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Unrecognized enrich policy type [{}]” class name is EnrichPolicyRunner.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (typeAndFormat.format != null) {
 mapping.put("format"; typeAndFormat.format);
 }
 yield mapping;
 }
 default -> throw new ElasticsearchException("Unrecognized enrich policy type [{}]"; policy.getType());
 };
 }  private XContentBuilder createEnrichMapping(List> sourceMappings) {
 Map> fieldMappings = new HashMap<>();

 

 [ratemypost]

Opster
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.