[Bug]: old milvus version (2.4) cannot handle tantivy index built from multiple segments correctly

[SpadeA-Tang]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: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

Version 2.4 only supports building tantivy index of single segment so it reads them as if there's only one segment for any tantivy index.
However, index buliding node can be upgraded to 2.5 which builds tantivy index for multiple segments. When 2.4 query nodes load index built from them, they mishandle it.

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[yanliang567]

/assign @SpadeA-Tang
/unassign