AUTO CREATE INDEX SETTING getKey – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-7.15

Briefly, this error occurs when Elasticsearch tries to automatically create an index that doesn’t exist, but the auto-create index setting is disabled. This setting is often disabled to prevent accidental creation of unwanted indices. To resolve this issue, you can either enable the auto-create index setting by setting it to true, or manually create the index before trying to index documents into it. Alternatively, you can specify a pattern of indices for which auto-creation should be allowed, while keeping it disabled for others.

This guide will help you check for common problems that cause the log ” [” + AUTO_CREATE_INDEX_SETTING.getKey() + “] ([ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “[” + AUTO_CREATE_INDEX_SETTING.getKey() + “] ([” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new IndexNotFoundException("[" + AUTO_CREATE_INDEX_SETTING.getKey() + "] contains [-"
 + indexExpression + "] which forbids automatic creation of the index"; index);
 throw new IndexNotFoundException("[" + AUTO_CREATE_INDEX_SETTING.getKey() + "] ([" + autoCreate
 + "]) doesn't match"; index);
 }  AutoCreate getAutoCreate() {
 return autoCreate;