groot

/lgtm /approve

withDimension() is for vector field, no need to specify for array field. withIsDynamic() is for dynamic field, no need to specify for array field. withMaxLength() is for varchar field, no...

MilvusClient里有两个delete接口： R delete(@NonNull DeleteParam requestParam) R delete(DeleteIdsParam requestParam) 上面那个是原生的，下面那个是包了一层的所谓高级接口。 实际上你调用这个高级的delete时，内部那个原生的delete是成功返回了的。而当这个高级接口包装一个DeleteResponse返回的时候，是通过MutationResultWrapper.getInsertIDs()想拿id，实际上原生的delete接口并不返回被删除的id，所以这里就会抛出那个"No found insertIds, please check your requests" https://github.com/milvus-io/milvus-sdk-java/blob/3e8c58f7b2a3e314a8f3b8644ef3cb4b2bedf418/src/main/java/io/milvus/response/MutationResultWrapper.java#L69 我的建议是用原生的delete 接口。要知道的是，delete是个异步操作，当你发送一堆id过去之后，server端只是把delete request推送到pulsar就返回，所以客户端delete接口返回时并不知道到底有多少数据会被删除。所以只要那个R返回SUCCESS就可以认为delete请求以被server端接受，后面会异步处理。 ``` R deleteR = milvusClient.delete(DeleteParam.newBuilder() .withCollectionName(COLLECTION_NAME) .withExpr(ID_FIELD + "==1") .build());...

delete()返回的那个delete count没有什么用，server端只是简单地把要删除的id统计一下返回给客户端。实际真正删除了多少，在返回的时候是不知道的，因为是异步执行。

The address of the database is specified when you declaring a MilvusClient, and this address cannot be changed. If you want to connect to another database, declare a new MilvusClient...

If the "database" is db of milvus, MilvusClientV2 has the interface [useDatabase()](https://github.com/milvus-io/milvus-sdk-java/blob/756f9561a5394d6f60dd42790793f37a47031998/src/main/java/io/milvus/v2/client/MilvusClientV2.java#L111), which can switch to another database. The V1 MilvusClient doesn't have the ability. But if the "database" is...

The code change has been merged to this pr: https://github.com/milvus-io/milvus-sdk-cpp/pull/273 I will close this pr, thank you for your contribution.

Already done in v2.4.0: https://github.com/milvus-io/milvus-sdk-cpp/releases/tag/v2.4.0

rerun go-sdk

/run-cpu-e2e