-
Notifications
You must be signed in to change notification settings - Fork 3k
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]: restful bug #37370
Comments
/assign |
/unassign @yanliang567 |
@smellthemoon When field in a collection is set to default or nullable, the response body of the describe collection interface does not contain default or nullable information. |
has added it in the issue describe. |
#37370 Signed-off-by: lixinguo <xinguo.li@zilliz.com> Co-authored-by: lixinguo <xinguo.li@zilliz.com>
@zhuwenxing could you help to add some test about the issue? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is there an existing issue for this?
Environment
Current Behavior
when autoid but still insert pk, pk will just be ingnored, not throw err.
query json data, user will see the byte, not json format.
insert pass pk when autoid==true,but set dynamic field, will thought pk is in dynamic.
if pass more field, restful will just ignore those extra field.
add nullable and default value describe.
pass "$meta" when enable dynamic field should report error.
describe collection field should not contains "$meta"
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: