Hi,
elastic:master
← martijnvg:auto_create_action!
opened 01:34PM - 28 Apr 20 UTC
Currently the `TransportBulkAction` detects whether an index is missing and
the… n decides whether it should be auto created. The coordination of the
index creation also happens in the `TransportBulkAction` on the coordinating node.
This change adds a new transport action that the `TransportBulkAction` delegates to
if missing indices need to be created. The reasons for this change:
* Auto creation of data streams can't occur on the coordinating node.
Based on the index template (v2) either a regular index or a data stream should be created.
However if the coordinating node is slow in processing cluster state updates then it may be
unaware of the existence of certain index templates, which then can load to the
`TransportBulkAction` creating an index instead of a data stream. Therefor the coordination of
creating an index or data stream should occur on the master node. See #55377
* From a security perspective it is useful to know whether index creation originates from the
create index api or from auto creating a new index via the bulk or index api. For example
a user would be allowed to auto create an index, but not to use the create index api. The
auto create action will allow security to distinguish these two different patterns of
index creation.
This change adds the following new transport actions:
* `AutoCreateAction`, the `TransportBulkAction` redirects to this action and this action will actually create the index (instead of the `TransportCreateIndexAction`). Later via #55377, can improve the `AutoCreateAction` to also determine whether an index or data stream should be created.
The `create_index` index privilege is also modified, so that if this permission is granted then a user is also allowed to auto create indices. This change does not yet add an `auto_create` index privilege. A future change can introduce this new index privilege or modify an existing index / write index privilege.
Is a breaking change in Elasticsearch 7.8.0.
It removes the action indices:admin/create and introduces indices:admin/create_index
I was wondering if this is handled in 1.20.0 which adds support for 7.8.0?
If so, the actions list in documentation readonlyrest-docs/elasticsearch.md at master · beshu-tech/readonlyrest-docs · GitHub should be updated to reflect this.
With kind regards,
Ronald
1 Like
coutoPL
(Mateusz Kołodziejczyk)
July 20, 2020, 4:29pm
2
IMO you can use new action in actions
rule without worries.
1 Like