[Enhancement]: Remove set replica_number logic in sdk #34355
Assignees
Labels
kind/enhancement
Issues or changes related to enhancement
Comments
|
/assign |
This was referenced Jul 2, 2024
sre-ci-robot
pushed a commit
to milvus-io/pymilvus
that referenced
this issue
Jul 4, 2024
issue: milvus-io/milvus#34355 Signed-off-by: Wei Liu <[email protected]>
weiliu1031
added a commit
to weiliu1031/pymilvus
that referenced
this issue
Jul 4, 2024
…io#2163) issue: milvus-io/milvus#34355 Signed-off-by: Wei Liu <[email protected]>
sre-ci-robot
pushed a commit
to milvus-io/milvus-sdk-go
that referenced
this issue
Jul 4, 2024
issue: milvus-io/milvus#34355 Signed-off-by: Wei Liu <[email protected]>
sre-ci-robot
pushed a commit
to milvus-io/pymilvus
that referenced
this issue
Jul 4, 2024
…2167) issue: milvus-io/milvus#34355 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
Is there an existing issue for this?
What would you like to be added?
when sdk try to load collection, and if user doesn't pass
replica_numberparam, sdk will just setreplica_number=1, which make collection load 1 replica by default.after we support to config database level props, we wonder if user doesn't pass
replica_numberparam, just let milvus decide to use database level config or just setreplica_number=1Why is this needed?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: