Do not create the missing index when invoking getRole #39039
Conversation
albertzaharovits
added
>non-issue
:Security/Security
|
Pinging @elastic/es-security |
|
For the PR bwc failure https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+pull-request-bwc/232/consoleFull we don't have the nodes' logs . I presume this is on purpose, and I have raised a discussion over Slack about it, but I won't mute because it is very unlikely the limited failure log information would lead to a fix and unmute (it looks like a cluster state timeout with an unassigned shard). 🎲 @elasticmachine run elasticsearch-ci/bwc |
Aaaargh, the cast_die is tripping locale conversions... @elasticmachine run elasticsearch-ci/bwc |
albertzaharovits
changed the title
albertzaharovits
deleted the
index-read-does-not-create-index-get-role
branch
* master: Mute failing CCR retention lease unfollow test Add support for ccr follow info api to HLRC. (elastic#39115) Do not create the missing index when invoking getRole (elastic#39039) Relax history check in ShardFollowTaskReplicationTests (elastic#39162) Add retention leases replication tests (elastic#38857) Edits to text in Phrase Suggester doc (elastic#38966) Edits to text in API Conventions docs (elastic#39001)
* master: Mute failing CCR retention lease unfollow test Add support for ccr follow info api to HLRC. (elastic#39115) Do not create the missing index when invoking getRole (elastic#39039) Relax history check in ShardFollowTaskReplicationTests (elastic#39162) Add retention leases replication tests (elastic#38857) Edits to text in Phrase Suggester doc (elastic#38966) Edits to text in API Conventions docs (elastic#39001)
In most of the places we avoid creating the `.security` index (or updating the mapping) for read/search operations. This is more of a nit for the case of the getRole call, that fixes a possible mapping update during a get role, and removes a dead if branch about creating the `.security` index.
In most of the places we avoid creating the `.security` index (or updating the mapping) for read/search operations. This is more of a nit for the case of the getRole call, that fixes a possible mapping update during a get role, and removes a dead if branch about creating the `.security` index.
In most of the places we avoid creating the `.security` index (or updating the mapping) for read/search operations. This is more of a nit for the case of the getRole call, that fixes a possible mapping update during a get role, and removes a dead if branch about creating the `.security` index.
In most of the places we avoid creating the `.security` index (or updating the mapping) for read/search operations. This is more of a nit for the case of the getRole call, that fixes a possible mapping update during a get role, and removes a dead if branch about creating the `.security` index.
In most of the places we avoid creating the
.securityindex (or updating the mapping) for read/search operations. This is more of a nit for the case of the getRole call, that fixes a possible mapping update during a get role, and removes a dead if branch about creating the.securityindex.