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

Question: clarify error message returned by Vitess rhs of an In operation should be a tuple #17789

Open
mcrauwel opened this issue Feb 14, 2025 · 3 comments
Labels
Component: Query Serving Type: Enhancement Logical improvement (somewhere between a bug and feature) Type: Question

Comments

@mcrauwel
Copy link
Contributor

Question

During testing we hit an issue where Vitess returned an error message that we could not really understand what the actual issue was. Would it be possible to clarify the error scenario so the message is clear as for what the actual problem is?

Message:

rhs of an In operation should be a tuple
@mcrauwel mcrauwel added Needs Triage This issue needs to be correctly labelled and triaged Type: Question labels Feb 14, 2025
@mattlord mattlord added Type: Enhancement Logical improvement (somewhere between a bug and feature) Component: Query Serving and removed Needs Triage This issue needs to be correctly labelled and triaged labels Feb 14, 2025
@kairveeehh
Copy link

hii , would like to take up this issue , had a few questions

  1. how would there be specific error messages displayed , like specific for each error encountered and a default for other or something else?

@systay
Copy link
Collaborator

systay commented Mar 3, 2025

Could you share the kind of query that triggers this error?

@kairveeehh
Copy link

Could you share the kind of query that triggers this error?

Ig it means that for anywhere error is encountered the messages should be readable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Query Serving Type: Enhancement Logical improvement (somewhere between a bug and feature) Type: Question
Projects
None yet
Development

No branches or pull requests

4 participants