[Feature Request] Apply settings on alias should get applied automatically on future indexes under the alias

[vishal-genea]

Is your feature request related to a problem? Please describe

Suppose I have created the index template with alias name : index_alias
Index pattern which is available under this alis is like : test_index_name_*

So all the index starting with "test_index_name_" will fall under the alias "index_alias" for the index template.

But now I want to apply any cluster related setting on the alias "index_alias", then it is not applicable to the index which will get created after applying the setting.

Describe the solution you'd like

So, my suggestion is, if we have applied the setting like

{ "max_inner_result_window": 4000 }

on alias index_alias, then if any index I create after applying this setting, should also get applied on this new index.

Currently as per my observation, if we apply the setting on the alias then it will only apply the setting on all the existing index only. If in future I am creating the index under this alias, then those setting should get automatically applied on this new index without hitting the setting again, otherwise creating the index template won't make sense because somtimes index gets created dynamically and we do not know about the creation, but if it get created same setting should be there.

Please look into it.

Related component

Other

Describe alternatives you've considered

No response

Additional context

No response

[mgodwan]

Index template already solves this problem.

1. Index templates put can be used to provide settings which you'd want to apply on the future indices created from the index template.
2. For applying the settings on indices already created from the template, you can continue using index name/alias.

[vishal-genea]

Yes.
All other configuration like shards, replicas, mappings gets applied to the future index also. But specifically the cluster settings like the example I have mentioned, that is not getting applied.