Epoch formatter is not supported as dynamic date format – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when you try to use an unsupported date format in Elasticsearch. The “epoch” format is not recognized as a dynamic date format. To resolve this issue, you can either use a supported date format like “epoch_millis” or “epoch_second” which are supported by Elasticsearch. Alternatively, you can convert your date to a format that Elasticsearch recognizes before indexing your documents.

This guide will help you check for common problems that cause the log ” Epoch [” + formatter + “] is not supported as dynamic date format ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “Epoch [” + formatter + “] is not supported as dynamic date format” class name is RootObjectMapper.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (fieldName.equals("date_formats") || fieldName.equals("dynamic_date_formats")) {
 if (fieldNode instanceof List) {
 List formatters = new ArrayList<>();
 for (Object formatter : (List) fieldNode) {
 if (formatter.toString().startsWith("epoch_")) {
 throw new MapperParsingException("Epoch [" + formatter + "] is not supported as dynamic date format");
 }
 formatters.add(parseDateTimeFormatter(formatter));
 }
 builder.dynamicDateTimeFormatter(formatters);
 } else if ("none".equals(fieldNode.toString())) {

 

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?