xige-16

Results 88 comments of xige-16

same with https://github.com/milvus-io/milvus/issues/21251

/assign @jingkl the issue should has been fixed since milvus 2.2.7

On Linux, read() (and similar system calls) will transfer at most 0x7ffff000 (2,147,479,552) bytes, returning the number of bytes actually transferred. (This is true on both 32-bit and 64-bit systems.)....

![image](https://github.com/milvus-io/milvus/assets/20124155/8b16aa23-e334-46cb-99e9-085327d83c7d)

the err message has been changed to "dim out of range: [32, 32768]" releated pr https://github.com/milvus-io/milvus/pull/23903

[querynode/cgo_helper.go:56] ["LoadFieldData failed, C Runtime Exception: [UnexpectedError] Assert \"suc\" at /go/src/github.com/milvus-io/milvus/internal/core/src/segcore/segment_c.cpp:208\n => unmarshal field data string failed\n"] https://github.com/milvus-io/milvus/blob/99975ec7f9d109f8c4598c9b4dfcb16d72627d27/internal/core/src/segcore/segment_c.cpp#L201-L216

The varChar scalar filed is indexed, so the LoadFieldData interface should not be called, and UpdateSealedSegmentIndex func should be called https://github.com/milvus-io/milvus/blob/99975ec7f9d109f8c4598c9b4dfcb16d72627d27/internal/core/src/segcore/segment_c.cpp#L236-L247