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

[Feature]: More informative error messages on inserting to collection #16536

Closed
1 task done
jmugan opened this issue Apr 19, 2022 · 5 comments
Closed
1 task done

[Feature]: More informative error messages on inserting to collection #16536

jmugan opened this issue Apr 19, 2022 · 5 comments
Assignees
Labels
kind/feature Issues related to feature request from users
Milestone

Comments

@jmugan
Copy link

jmugan commented Apr 19, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe.

Inserting vectors into a collection requires a lot of fumbling in the dark.

Describe the solution you'd like.

My vectors are in numpy and I have to convert them to a list, but I keep getting errors like pymilvus.orm.exceptions.DataTypeNotSupportException: <DataTypeNotSupportException: (code=0, message=Data type is not support.)> or pymilvus.orm.exceptions.SchemaNotReadyException: <SchemaNotReadyException: (code=0, message=The types of schema and data do not match.)>.

It reminds me of the matrix size mismatch problem in deep learning, but PyTorch and TensorFlow will say something like "expected xyz" and got "xyk" to help clue you in on what is going on.

Describe an alternate solution.

No response

Anything else? (Additional Context)

No response

@jmugan jmugan added the kind/feature Issues related to feature request from users label Apr 19, 2022
@XuanYang-cn
Copy link
Contributor

@jmugan Good advice!
/assign
/unassign @xiaofan-luan

@xiaofan-luan
Copy link
Collaborator

but PyTorch and TensorFlow will say something like "expected xyz" and got "xyk" to help clue you in on what is going on.

Emmm, feel free to send pull request, the current error message is confusing~

@stale
Copy link

stale bot commented Jun 4, 2022

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.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Jun 4, 2022
@xiaofan-luan
Copy link
Collaborator

keep it open

@stale stale bot removed the stale indicates no udpates for 30 days label Jun 5, 2022
@xiaofan-luan xiaofan-luan added stale indicates no udpates for 30 days and removed stale indicates no udpates for 30 days labels Jun 5, 2022
@XuanYang-cn XuanYang-cn added this to the 2.2 milestone Oct 31, 2022
XuanYang-cn added a commit to XuanYang-cn/pymilvus that referenced this issue Nov 7, 2022
XuanYang-cn added a commit to XuanYang-cn/pymilvus that referenced this issue Nov 8, 2022
sre-ci-robot pushed a commit to milvus-io/pymilvus that referenced this issue Nov 8, 2022
@XuanYang-cn
Copy link
Contributor

fixed at pymilvus==2.2.0, Feel free to reopen this if anything similar occurs again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Issues related to feature request from users
Projects
None yet
Development

No branches or pull requests

3 participants