[Bug]: TempIndex failed to process the data already persisted within the growing segment.

[czs007]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version:Master & 2.5 & 2.4
- 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

We have two types of growing segments:

1. Data located after the shard leader's consumption checkpoint, where the shard leader will consume the first message of the segment, then create the growing segment. This is not an issue, and subsequent inserts will be directed to TempIndex.
2. Data that is entirely or partially located before the shard leader's checkpoint (meaning some of it has already been committed to object storage). This segment is created during the invocation of the watch channel for the shard leader, specifying the segment ID and data path. The data within these files needs to be integrated into the temporary index.

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response