-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
update RewriterConstants so that expr min max would not collide with columns start with "parent" #13357
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #13357 +/- ##
============================================
+ Coverage 61.75% 61.99% +0.24%
+ Complexity 207 198 -9
============================================
Files 2436 2550 +114
Lines 133233 140257 +7024
Branches 20636 21801 +1165
============================================
+ Hits 82274 86958 +4684
- Misses 44911 46702 +1791
- Partials 6048 6597 +549
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
update enums and fix tests update RewriterConstants
08bbe70
to
1e905a3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks for making the fix!
Updated RewriterConstants so that expr min max would not collide with columns start with "parent", tested with unit tests. In production we have turned this on for some cluster having user queries like
select parent_ from Table
. These queries collided with the rewriter's flag for parent aggregation function and will run into exceptions likeTagging this
backward incompat
as it requires to deploy server and broker to the same version to make theexprmin/exprmax
queries run correctly.