binbin
binbin
Same issue in the following nightly: https://jenkins.milvus.io:18080/blue/organizations/jenkins/Milvus%20Nightly%20CI/detail/master/11/pipeline (1) milvus logs: [artifacts-milvus-distributed-kafka-nightly-11-pymilvus-e2e-logs.tar.gz](https://jenkins.milvus.io:18080/job/Milvus%20Nightly%20CI/job/master/11/artifact/artifacts-milvus-distributed-kafka-nightly-11-pymilvus-e2e-logs.tar.gz) (2) collection name: test_GQu207FX (just one example for "test_release_collection_not_existed") (3) FAILED time: [2022-08-02T15:05:17.249Z] [gw0] [ 9%] FAILED testcases/test_collection.py::TestLoadCollection::test_load_collection_after_index [2022-08-02T15:05:17.249Z]...
/lgtm /approve
Fixed in 2.2.0.dev72 (pymilvus) pymilvus.exceptions.DataNotMatchException:
@XuanYang-cn any updates?
This still exists in the latest version: pymilvus: 2.4.0rc30 milvus: master-20240205-a68b3213 ``` >>> milvus_client.create_collection(collection_name, dim, consistency_level="Strong", metric_type="L2") >>> res = milvus_client.get_collection_stats(collection_name) >>> print(res) {'row_count': 0} ```
/assign @Presburger /unassign @yanliang567
@ThreadDao is it verified and fixed?
/assign @czs007
latest statistics standalone: 16c64g, dataset: 10M, dim=768 scalar clustering: (open source image) major compaction: about 15min waiting index time for new segments: about 48min.