Skip to content
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

[Enhancement]: Enable resource group API in milvus client #38739

Open
1 of 6 tasks
weiliu1031 opened this issue Dec 25, 2024 · 1 comment
Open
1 of 6 tasks

[Enhancement]: Enable resource group API in milvus client #38739

weiliu1031 opened this issue Dec 25, 2024 · 1 comment
Assignees
Labels
kind/enhancement Issues or changes related to enhancement

Comments

@weiliu1031
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to be added?

Enable resource group API in milvus client

  • pymilvus
  • go-sdk
  • java-sdk
  • nodejs-sdk
  • restful

Why is this needed?

No response

Anything else?

No response

@weiliu1031 weiliu1031 added the kind/enhancement Issues or changes related to enhancement label Dec 25, 2024
@weiliu1031
Copy link
Contributor Author

/assign

sre-ci-robot pushed a commit to milvus-io/pymilvus that referenced this issue Dec 25, 2024
issue: milvus-io/milvus#38739
this PR enable those API in milvus client:
- create_resource_group
- update_resource_groups
- drop_resource_group
- describe_resource_group
- list_resource_groups
- transfer_replica

cause the resource group prefer to use declarative api, so the
transfer_node API is deprecated in milvus client, it's recommand to use
update_resource_group to manage node num in resource group.

Signed-off-by: Wei Liu <[email protected]>
weiliu1031 added a commit to weiliu1031/pymilvus that referenced this issue Dec 26, 2024
issue: milvus-io/milvus#38739
this PR enable those API in milvus client:
- create_resource_group
- update_resource_groups
- drop_resource_group
- describe_resource_group
- list_resource_groups
- transfer_replica

cause the resource group prefer to use declarative api, so the
transfer_node API is deprecated in milvus client, it's recommand to use
update_resource_group to manage node num in resource group.

Signed-off-by: Wei Liu <[email protected]>
weiliu1031 added a commit to weiliu1031/pymilvus that referenced this issue Dec 26, 2024
issue: milvus-io/milvus#38739
this PR enable those API in milvus client:
- create_resource_group
- update_resource_groups
- drop_resource_group
- describe_resource_group
- list_resource_groups
- transfer_replica

cause the resource group prefer to use declarative api, so the
transfer_node API is deprecated in milvus client, it's recommand to use
update_resource_group to manage node num in resource group.

Signed-off-by: Wei Liu <[email protected]>
sre-ci-robot pushed a commit to milvus-io/pymilvus that referenced this issue Dec 26, 2024
issue: milvus-io/milvus#38739
pr: #2513
this PR enable those API in milvus client:
- create_resource_group
- update_resource_groups
- drop_resource_group
- describe_resource_group
- list_resource_groups
- transfer_replica

cause the resource group prefer to use declarative api, so the
transfer_node API is deprecated in milvus client, it's recommand to use
update_resource_group to manage node num in resource group.

Signed-off-by: Wei Liu <[email protected]>
sre-ci-robot pushed a commit to milvus-io/pymilvus that referenced this issue Dec 26, 2024
issue: milvus-io/milvus#38739
pr: #2513
this PR enable those API in milvus client:
- create_resource_group
- update_resource_groups
- drop_resource_group
- describe_resource_group
- list_resource_groups
- transfer_replica

cause the resource group prefer to use declarative api, so the
transfer_node API is deprecated in milvus client, it's recommand to use
update_resource_group to manage node num in resource group.

Signed-off-by: Wei Liu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Issues or changes related to enhancement
Projects
None yet
Development

No branches or pull requests

1 participant