Global composable templates may not specify the setting – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” global composable templates may not specify the setting ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata and cluster.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “global composable templates may not specify the setting”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public static void validateV2TemplateRequest(Metadata metadata; String name; ComposableIndexTemplate template) {
 if (template.indexPatterns().stream().anyMatch(Regex::isMatchAllPattern)) {
 Settings mergedSettings = resolveSettings(metadata; template);
 if (IndexMetadata.INDEX_HIDDEN_SETTING.exists(mergedSettings)) {
 throw new InvalidIndexTemplateException(name; "global composable templates may not specify the setting "
 + IndexMetadata.INDEX_HIDDEN_SETTING.getKey());
 final Map componentTemplates = metadata.componentTemplates();


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content