-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
TYPE_MISMATCH exception for in operator with single column tuples. #49844
TYPE_MISMATCH exception for in operator with single column tuples. #49844
Conversation
This is an automated comment for commit 8c7b63f with description of existing statuses. It's updated for the latest CI running
|
Also it will be great to backport this patch. Is it possible? |
… single column tuples.
… single column tuples.
… single column tuples.
Backport #49844 to 23.3: TYPE_MISMATCH exception for in operator with single column tuples.
We should not backport non-essential patches because it puts LTS versions at risk. |
Agree. But this one is about backward-incompatibility. We caught this after upgrading a ClickHouse cluster from 22.3 to 22.8. |
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Add support for (an unusual) case where the arguments in the
IN
operator are single-element tuples.Reproduce:
Result:
Documentation entry for user-facing changes