[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
Labels
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
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
The text was updated successfully, but these errors were encountered: