[Bug]: MetaCache maybe polutated across clients when different client connect to different database #809
Assignees
Comments
congqixia
added a commit
to congqixia/milvus-sdk-go
that referenced
this issue
Aug 21, 2024
Related to milvus-io#809 Signed-off-by: Congqi Xia <congqi.xia@zilliz.com>
sre-ci-robot
pushed a commit
that referenced
this issue
Aug 21, 2024
sre-ci-robot
pushed a commit
to milvus-io/milvus
that referenced
this issue
Aug 29, 2024
Related to milvus-io/milvus-sdk-go#809 --------- Signed-off-by: Congqi Xia <congqi.xia@zilliz.com>
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?
Current Behavior
MetaCacheis process-wide singleton and shared between clients. Even the clients are connected to different instance or databases.Expected Behavior
MetaCache shall be client-wise.
Steps To Reproduce
No response
Environment
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: