[Bug]: Forgetting to set blob memory size when compaction resulted a huge segment being generated

[xiaocai2333]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version:master
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Forgetting to set blob memory size when compaction resulted a huge segment being generated.

the segment max size config size is 1024M, but generated the segment with num rows is 3080000, and the dim is 768.
from the birdwatcher, all the segment after compaction, the memory size is 0.

Expected Behavior

should be set blob memory size in

milvus/internal/storage/serde.go

Lines 927 to 931 in 310bfe7

	return &Blob{
	Key: strconv.Itoa(int(bsw.fieldSchema.FieldID)),
	Value: b.Bytes(),
	RowNum: int64(bsw.rw.numRows),
	}, nil

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[xiaocai2333]

/assign @tedxu
/unassign @yanliang567

[xiaocai2333]

fixed
/close

[sre-ci-robot]

@xiaocai2333: Closing this issue.

In response to this:

fixed
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.