[Bug]: [null & default] The "nullable" property is lost and data is not "None" when migrating the collection with the nullable fields from 2.x to 2.x #36346
- Milvus version: from master-latest to master-latest
- Deployment mode(standalone or cluster): both
- MQ type(rocksmq, pulsar or kafka): all
- SDK version(e.g. pymilvus v2.0.0rc2):2.5.0rc78
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
Current Behavior
The "nullable" property is lost and data is not "None" when migrate the collection with the nullable fields from 2.x to 2.x
before migration:
Is there an existing issue for this?
Environment
Current Behavior
The "nullable" property is lost and data is not "None" when migrate the collection with the nullable fields from 2.x to 2.x before migration:
After migration:
Expected Behavior
Data with "None" is not lost
Steps To Reproduce
Milvus Log
No response
Anything else?
No response