When I try to run client.search() on my collection, I get the following error:

Hello I’m a newbie in using milvus-backup tool
Milvus version: from 2.3.12
Deployment mode(standalone or cluster): cluster
milvus-backup version: v0.4.14

I am working on a patch to add PowerPC optimization to the Milvus Knowhere source tree. I have add the new files:

The advanced filters described in this document: https://milvus.io/docs/array_data_type.md (ARRAY_CONTAINS, ARRAY_CONTAINS_ALL, ARRAY_CONTAINS_ANY, and ARRAY_LENGTH) require a filter field in the arguments of client.search or client.query. I don’t see this filter argument in the search and query source code.

Message queue is a key component for Milvus.
For Milvus cluster, Pulsar is the message queue.
For Milvus standalone, a RocksDB is embedded in milvus, and the data path of the RocksDB is rbd_data. sst file is RocksDB file format.

java的sdk版本：2.2.13
milvus版本：2.2.16

[2024/06/13 10:52:55.099 +08:00] [WARN] [proxy/task_search.go:652] [“failed to requery”] [traceID=f500fbe139528473d59e08b8831fc8da] [nq=1] [error=”incomplete query result, missing id 202406020002_f83813dceb954132aff00edb2139ffa1_1_A8F79679-8177-194C-8D3D-CA0D82865B48_1, len(searchIDs) = 298, len(queryIDs) = 291, collection=450390723841055357: inconsistent requery result”] [errorVerbose=”incomplete query result, missing id 202406020002_f83813dceb954132aff00edb2139ffa1_1_A8F79679-8177-194C-8D3D-CA0D82865B48_1, len(searchIDs) = 298, len(queryIDs) = 291, collection=450390723841055357: inconsistent requery resultn(1) attached stack tracen — stack trace:n | github.com/milvus-io/milvus/pkg/util/merr.WrapErrInconsistentRequeryn | t/root/code/milvus/pkg/util/merr/utils.go:1038n | github.com/milvus-io/milvus/internal/proxy.doRequeryn | […]

so I deploy a milvus cluster 2.4 to awk eks, and was hoping to try out gpu indices. however when I try to create gpu index on a tiny collection I got something like

When running Milvus server from the deb file installation – it works OK, But when trying to run it from a custom build of standalone (without docker, with embedded etcd, with the same milvus.yaml file of the installation) – I am getting “RootCoordClient mess key not exist”. It seems that the RootCoord client is unable to find a necessary key in its configuration. Specifically, it’s indicating that a key named “rootcoord” does not exist, which the client is attempting to use. Anyone is familiar with this issue?

I am currently working with the following setup: