-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Support 'EXTRACT' as a scalar function #13463
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
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #13463 +/- ##
============================================
+ Coverage 61.75% 62.06% +0.31%
+ Complexity 207 198 -9
============================================
Files 2436 2559 +123
Lines 133233 141341 +8108
Branches 20636 21928 +1292
============================================
+ Hits 82274 87727 +5453
- Misses 44911 46950 +2039
- Partials 6048 6664 +616
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
However, the test itself seems a little odd because even before the changes from this PR, while the test passes (i.e., the query compiles to a v1 Pinot query), trying to run an actual query like @Jackie-Jiang can the test be updated to use timestamps in the form of milliseconds since epoch or is there some other missing context here? |
612a08c to
652f269
Compare
|
The only reason the test wasn't failing earlier was that since there was no scalar function for |
652f269 to
d24fb03
Compare
d24fb03 to
bf1120c
Compare
EXTRACTas scalar function #13462EXTRACTfunction since in the v2 engine, numerous functions are rewritten to a call to EXTRACT by Calcite.PinotEvaluateLiteralRuleis required to support the use of the new scalar function with literals in intermediate stages with the multi-stage query engine.