-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
List aliases API (rest & gRPC) #1363
Conversation
99e4c0b
to
a4f0fec
Compare
src/actix/api/collections_api.rs
Outdated
@@ -151,6 +158,7 @@ async fn update_collection_cluster( | |||
// Configure services | |||
pub fn config_collections_api(cfg: &mut web::ServiceConfig) { | |||
cfg.service(get_collections) | |||
.service(get_aliases) // higher priority than /collections/{name} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a subtle issue here, the get_aliases needs
must have a higher priority than get_collection
.
GET collections/aliases
vs GET collections/{name}
are conflicting with each other.
Maybe we should forbid the creation of collections name aliases
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WDYT about GET /aliases
for all aliases and GET /collections/<name>/aliases
for aliases associated with specified colelction?
Similar to /snapshots
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion 👍
Done in 4b6ef78
* List aliases API (rest & gRPC) * rework api to avoid conflicts
This PR adds a new API for listing existing collections aliases.
This change requires to update the clients to expose the new feature.