-
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
Datetime transform functions #8397
Datetime transform functions #8397
Conversation
I've reverted to JODA because I noticed that
|
Codecov Report
@@ Coverage Diff @@
## master #8397 +/- ##
=============================================
+ Coverage 30.54% 64.08% +33.53%
- Complexity 0 4275 +4275
=============================================
Files 1642 1610 -32
Lines 86112 84709 -1403
Branches 13000 12853 -147
=============================================
+ Hits 26304 54285 +27981
+ Misses 57420 26499 -30921
- Partials 2388 3925 +1537
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
95369f4
to
6c12951
Compare
This PR starts with a small refactoring to allow
TransformFunctionType
s to have aliases, then introducesTransformFunction
s for the following functions:year
yearOfWeek
yow
month
week
weekOfYear
quarter
dayOfWeek
dow
dayOfYear
doy
dayOfMonth
day
hour
minute
millisecond
The transform functions are tested against the
@ScalarFunction
s.The motivation for the change is the high cost of using scalar functions in transforms. Here is the allocation rate observed for
vs the similar
When scalar function is used, 16% of samples were in verifying accessibility of the
Method
-@ScalarFunction
should be used only as a last resort.