Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Alias Action #148

Open
dbbaughe opened this issue Feb 11, 2020 · 6 comments
Open

Alias Action #148

dbbaughe opened this issue Feb 11, 2020 · 6 comments
Labels
action Index management actions enhancement An improvement on the existing feature’s functionalities

Comments

@dbbaughe
Copy link
Contributor

During the community meeting, someone asked if it was possible to have an action to add an alias to the index.
Will use this issue to track it + see if other people are interested.

@dbbaughe dbbaughe added the enhancement An improvement on the existing feature’s functionalities label Feb 11, 2020
@dbbaughe dbbaughe added the action Index management actions label Jul 6, 2020
@dbbaughe
Copy link
Contributor Author

Hey @jasonrojas, @teddyphreak, and @dparker18

Do you have some examples of what you would be using this for? And any specific optional settings for the alias operation?

@samling
Copy link

samling commented Aug 11, 2020

One use case we have is for indices older than a certain age, we allocate them to a cold node, shrink them, delete the original and create an alias with the original name that points to the shrink index. This keeps our shard count down while not breaking queries for older data.

@dparker18
Copy link

My use case is when an index foo is shrunk, it becomes shrink-foo. An alias action would allow the new shrunk index to also be aliased to foo so applications don't know the difference. When we moved from x-pack and ILM to ISM, the aliasing had to be handled with custom code outside ES. I'd be just as happy with the alias being an optional setting on the shrink operation. Happy to share details, but what we're doing is pretty basic.

@jasonrojas
Copy link

my use case is around the shrinking of indices as well. But in general I think it would be great to support adding an alias, especially if we get to the stage where we can roll up indices into single indices then alias them with the ones that were rolled up.

@tharsha18
Copy link

My use case is, If we have an alias for an index with rollover ILM policy, can we remove it from alias after some predefined days, let's say 30 days? I know there is a way to delete an index once its old, but in our case we do not want to delete but want the index to be removed from alias and have the alias switch and point to indices whose age is less than 30 days.

@CharlesZ-Chen
Copy link

My use case is:

we provide search_alias to search our dataset. We publish new version of dataset every week as a new index (e.g. dataset-yyyy-MM-dd. We want the search_alias always pointing to the latest published dataset.
The process is:
ingest new data to a new index
once ingestion finish, re-pointing search_alias to the new index, remove old index from the search_alias

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action Index management actions enhancement An improvement on the existing feature’s functionalities
Projects
None yet
Development

No branches or pull requests

6 participants