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
Fix possible incorrect result of aggregate function uniqExact
#61257
Conversation
The issue was that #57872 introduced an optimization that calls |
This is an automated comment for commit e418f24 with description of existing statuses. It's updated for the latest CI running ❌ Click here to open a full report in a separate page
Successful checks
|
Profile event |
…647b50dd3d8f1ecaa80451b8986bd3 Cherry pick #61257 to 23.12: Fix possible incorrect result of aggregate function `uniqExact`
…function `uniqExact`
…47b50dd3d8f1ecaa80451b8986bd3 Cherry pick #61257 to 24.1: Fix possible incorrect result of aggregate function `uniqExact`
…47b50dd3d8f1ecaa80451b8986bd3 Cherry pick #61257 to 24.2: Fix possible incorrect result of aggregate function `uniqExact`
Backport #61257 to 23.12: Fix possible incorrect result of aggregate function `uniqExact`
Backport #61257 to 24.2: Fix possible incorrect result of aggregate function `uniqExact`
Backport #61257 to 24.1: Fix possible incorrect result of aggregate function `uniqExact`
I think we've just hit this issue (wrong Is there any chance that we'd see a new 24.2 series release with the backported fix? |
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Fix possible incorrect result of aggregate function
uniqExact
.