-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: [null & default] The "nullable" property is lost and data is not "None" after backup and restore the collection with the nullable fields #36341
Labels
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Comments
binbinlv
added
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
labels
Sep 18, 2024
sre-ci-robot
pushed a commit
that referenced
this issue
Sep 26, 2024
…36526) #36341 Signed-off-by: lixinguo <[email protected]> Co-authored-by: lixinguo <[email protected]>
/assign @wayblink |
related with zilliztech/milvus-backup#440, could you help to verify it? @binbinlv |
/assign |
working on verify |
Verified and fixed: (after the latest backup commit: Support nullable field and default value (#440)) before backup:
After backup and restore:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Issues or changes related a bug
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Is there an existing issue for this?
Environment
Current Behavior
The "nullable" property is lost and data is not "None" after backup the collection with the nullable fields
data from "None" to 0.0 for int field., and from "None" to '' for varchar field.
before backup:
After backup and restore:
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: