[Bug]: Load collection is failing for collection with sparse and dense vectors in 2.4 about milvus HOT 7 OPEN

thanks for your inputs.I'll see if i can spin up a new cluster and test this functionality out. What is weird is the standard operations were working

Object store is shared but I've specified a different root path. Need to check if there is something wrong with the config

from milvus.

Just to cross-check if there is an issue with milvus cluster, I ran hello_milvus.py which is returning the correct results and loading records correctly. Seems to be a bug with sparse vectors flow

from milvus.

/assign @liliu-z
/unassign

from milvus.

/assign @zhengbuqian

from milvus.

hi @kdabbir , can you try running the https://github.com/milvus-io/pymilvus/blob/master/examples/hello_sparse.py and the https://github.com/milvus-io/pymilvus/blob/master/examples/hello_hybrid_sparse_dense.py script and see if any error occurs?

I tried to reproduce the error by running your script against my milvus standalone and got no error. From query worker logs I see tons of I20240502 17:29:38.770249 128 Utils.cpp:825] [SERVER][LoadFieldDatasFromRemote][milvus] failed to load data from remote: Error in GetObjectSize[errcode:404, exception:, errmessage:No response body., params:params, bucket=perf2-uswest2-cdp1-dpc-milvus, object=milvus-storage/milvus2379test/insert_log/449477877573946718/449477877573946719/449477877574146799/0/449477877575149847], this could be related.

from milvus.

@kdabbir did your instance share the object storage with other milvus instance?

from milvus.

To supplement @congqixia , the error log basically indicates the segment object file is not found(code 404) in the s3 bucket, causing the load to fail.

from milvus.