Skip to content
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]: Create Collection failed If varchar field has type params other than max_length #25206

Closed
1 task done
xige-16 opened this issue Jun 28, 2023 · 0 comments
Closed
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@xige-16
Copy link
Contributor

xige-16 commented Jun 28, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

When using milvus to create FieldSchema of type VarChar, if you specify type params other than max_length, an error will be reported "type param key (max_length) should be specified for varChar field"

Expected Behavior

ignore other useless type params

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@xige-16 xige-16 added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 28, 2023
@xige-16 xige-16 changed the title [Bug]: [Bug]: Create Collection failed If varchar field has type params other than max_length Jun 28, 2023
@xige-16 xige-16 assigned xige-16 and unassigned yanliang567 Jun 28, 2023
This was referenced Jun 28, 2023
@xige-16 xige-16 closed this as completed Jul 5, 2023
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 needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants