Nested type name does not support subobjects parameter – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.3-8.9

Briefly, this error occurs when you’re trying to use the [subobjects] parameter in a nested type field in Elasticsearch. Nested types do not support this parameter. To resolve this issue, you can either remove the [subobjects] parameter from the nested type field or change the field type to one that supports [subobjects], such as ‘object’ type. Alternatively, you can restructure your data to avoid the need for nested subobjects.

This guide will help you check for common problems that cause the log ” Nested type [” + name + “] does not support [subobjects] parameter ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “Nested type [” + name + “] does not support [subobjects] parameter” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public static class TypeParser extends ObjectMapper.TypeParser {
 public Mapper.Builder parse(String name; Map node; MappingParserContext parserContext)
 throws MapperParsingException {
 if (parseSubobjects(node).explicit()) {
 throw new MapperParsingException("Nested type [" + name + "] does not support [subobjects] parameter");
 NestedObjectMapper.Builder builder = new NestedObjectMapper.Builder(name; parserContext.indexVersionCreated());
 parseNested(name; node; builder);
 for (Iterator> iterator = node.entrySet().iterator(); iterator.hasNext();) {
 Map.Entry entry =;


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?