Field n of type type can t be used in multifields – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.14-8.9

Briefly, this error occurs when you try to use a field type in a multifield that is not supported by Elasticsearch. Multifields are used to index a single field in different ways, but not all field types are compatible. To resolve this issue, you can either change the field type to one that is compatible with multifields, or remove the field from the multifield configuration. Alternatively, you can create a separate field with the desired type and use a copy_to directive to copy the values from the original field.

This guide will help you check for common problems that cause the log ” Field [” + n + “] of type [” + type + “] can’t be used in multifields ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “Field [” + n + “] of type [” + type + “] can’t be used in multifields” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  public static BiConsumer notInMultiFields(String type) {
 return (n; c) -> {
 if (c.isWithinMultiField()) {
 throw new MapperParsingException("Field [" + n + "] of type [" + type + "] can't be used in multifields");
 }  /**


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?