Skip to content
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

evalengine: Implement LAST_DAY #15038

Merged
merged 4 commits into from
Jan 26, 2024
Merged

evalengine: Implement LAST_DAY #15038

merged 4 commits into from
Jan 26, 2024

Conversation

beingnoble03
Copy link
Member

Description

This PR adds implementation of LAST_DAY func in evalengine.

Related Issue(s)

Fixes part of #9647

Checklist

  • "Backport to:" labels have been added if this change should be back-ported to release branches
  • If this change is to be back-ported to previous releases, a justification is included in the PR description
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on CI?
  • Documentation was added or is not required

Deployment Notes

Copy link
Contributor

vitess-bot bot commented Jan 25, 2024

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot added NeedsBackportReason If backport labels have been applied to a PR, a justification is required NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsIssue A linked issue is missing for this Pull Request NeedsWebsiteDocsUpdate What it says labels Jan 25, 2024
@github-actions github-actions bot added this to the v19.0.0 milestone Jan 25, 2024
Copy link

codecov bot commented Jan 25, 2024

Codecov Report

Attention: 20 lines in your changes are missing coverage. Please review.

Comparison is base (1bf8dda) 47.36% compared to head (c24efc8) 47.49%.
Report is 19 commits behind head on main.

Files Patch % Lines
go/vt/vtgate/evalengine/cached_size.go 0.00% 10 Missing ⚠️
go/vt/vtgate/evalengine/compiler_asm.go 71.42% 3 Missing and 1 partial ⚠️
go/vt/vtgate/evalengine/fn_time.go 92.50% 2 Missing and 1 partial ⚠️
go/vt/vtgate/evalengine/translate_builtin.go 40.00% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15038      +/-   ##
==========================================
+ Coverage   47.36%   47.49%   +0.13%     
==========================================
  Files        1144     1149       +5     
  Lines      238995   239387     +392     
==========================================
+ Hits       113197   113700     +503     
+ Misses     117213   117092     -121     
- Partials     8585     8595      +10     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@systay systay added Type: Enhancement Logical improvement (somewhere between a bug and feature) Component: Query Serving and removed NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says NeedsIssue A linked issue is missing for this Pull Request NeedsBackportReason If backport labels have been applied to a PR, a justification is required labels Jan 25, 2024
@systay
Copy link
Collaborator

systay commented Jan 25, 2024

Hi @beingnoble03!

You need to run make codegen and then commit & push the changes.

That's why the static checks are failing

@@ -1200,6 +1205,54 @@ func (call *builtinMonthName) compile(c *compiler) (ctype, error) {
return ctype{Type: sqltypes.VarChar, Col: col, Flag: arg.Flag | flagNullable}, nil
}

func lastDay(dt datetime.DateTime) (datetime.Date, bool) {
ts := dt.Date.ToStdTime(time.Local)
firstDayOfNextMonth := time.Date(ts.Year(), ts.Month()+1, 1, 0, 0, 0, 0, time.Local)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

time.Local here should be the current timezone from the environment. Looks like that is wrong in more places, we should fix those all up then.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@beingnoble03 If you want, I can also push up fixes for the other spots that use time.Local, or you can do it, whatever you prefer really.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dbussink I think I can do that. I'll push the changes.

func lastDay(dt datetime.DateTime) (datetime.Date, bool) {
ts := dt.Date.ToStdTime(time.Local)
firstDayOfNextMonth := time.Date(ts.Year(), ts.Month()+1, 1, 0, 0, 0, 0, time.Local)
lastDayOfMonth := firstDayOfNextMonth.AddDate(0, 0, -1)
Copy link
Contributor

@dbussink dbussink Jan 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should do the addition with ts.AddDate(0, 1, -1) as well and not do that in time.Date (the ts.Month()+1 bit) to make it easier to follow and to avoid the question of "how does it work if the month is already December".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

got it. done.

func FnLastDay(yield Query) {
for _, d := range inputConversions {
yield(fmt.Sprintf("LAST_DAY(%s)", d), nil)
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Next to these inputs, we should also test it against a few more inputs explicitly to test edge case behaviors here. Like last of December, January & February years (with / without leap years etc).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

@beingnoble03
Copy link
Member Author

@systay thanks. done.

@@ -756,7 +756,7 @@ func (call *builtinHour) compile(c *compiler) (ctype, error) {
return ctype{Type: sqltypes.Int64, Col: collationNumeric, Flag: arg.Flag | flagNullable}, nil
}

func yearDayToTime(y, yd int64) time.Time {
func yearDayToTime(env *ExpressionEnv, y, yd int64) time.Time {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it’s best to pass in the most specific type. So we should pass in the time zone itself here I think.

Same applies to lastday as well.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

Copy link
Collaborator

@systay systay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice work!

}

d := lastDay(env.currentTimezone(), dt.dt)
if d.IsZero() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this case happen? We already check above that it's not nil or a zero date, so how could it be a zero date here? I think we can remove this check (and the equivalent one from the compiler)?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm... true. This can not happen. Removed from here.
But I didn't add a check for zero datetime before calling lastDay in compiler_asm. And, there's no check in lastDay func for checking that, so added a check before calling lastDay and removed the check after that, as it was unnecessary.

@dbussink dbussink merged commit 44d6a6b into vitessio:main Jan 26, 2024
102 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Query Serving Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants