-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Make start and end timestamps tz aware in the CLI #1590
Conversation
Signed-off-by: Achal Shah <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #1590 +/- ##
=======================================
Coverage 83.60% 83.60%
=======================================
Files 65 65
Lines 5757 5758 +1
=======================================
+ Hits 4813 4814 +1
Misses 944 944
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Signed-off-by: Achal Shah <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: achals, woop The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
* Make start and end timestamps tz aware in the CLI Signed-off-by: Achal Shah <[email protected]> * make format Signed-off-by: Achal Shah <[email protected]>
What this PR does / why we need it:
We log start and time information in the CLI, before converting the timestamps into tz-aware datetime objects. This results in a confusion when running
feast materialize-incremental
which only takes in an end_ts argument. The end_ts argument is tz-naive, but start_ts is tz-aware, which causes the time range that's logged to the console to be messed up.This PR changes the behaviour to add tz information at the boundary of the CLI so that log messages in the deeper classes as well as in the CLI are consistent.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: