-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Index Alias management capabilities #162
Comments
@pierrelambert 100% Agreed - this is planned for the Ideally the index alias would be a schema property like this: index:
name: users_v1
prefix: user
alias: users
fields:
- name: user
type: tag
- name: credit_score
type: tag So then the alias would get added transparently as they call And then a new command to update the alias: index.update_alias("new_alias_name") However, given we can't trace the state of the index<>alias relationships... this is pretty much impossible without footguns all over the place. @bsbodden curious on your take? |
Define / Set an alias to an index is must have. |
I agree with @pierrelambert that this is a must have for prod environments, since the index to alias relationship is a one-to-many we could:
|
I like this approach. I’ve been hesitant to create extra “metadata” generated by the library… but I think I agree that usability and functionality is most important here. We need alias support for sure. I’ll start working on a more detailed write up for this. |
The Alias capability of Indexes with ft.aliasadd, ft.aliasdel, FT.ALIASUPDATE permits agility in making index and apps evolving.
Would be nice to be able to handle this at SearchIndex level directly.
The text was updated successfully, but these errors were encountered: