-
Notifications
You must be signed in to change notification settings - Fork 328
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
feat!: do not get TZ info from server local env #2905
Conversation
Signed-off-by: Ruihang Xia <waynestxia@gmail.com>
Signed-off-by: Ruihang Xia <waynestxia@gmail.com>
Signed-off-by: Ruihang Xia <waynestxia@gmail.com>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #2905 +/- ##
===========================================
- Coverage 85.01% 84.52% -0.50%
===========================================
Files 753 756 +3
Lines 118592 119453 +861
===========================================
+ Hits 100820 100966 +146
- Misses 17772 18487 +715 |
@waynexia Is this a breaking change? |
Yes, I've changed the title |
A user says he's using Influxdb line protocol with explicit timestamp to write, and read with timestamp (instead of the date time like "2023-12-12 17:45:00"). So I think this breaking change is fine. |
Let's move on! |
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Remove the logic of fetching server's local timezone as the default timezone. Use Zulu (UTC+0) by default. We can provide a method to set per-session timezone in the future, as requested in #2893
Warning
This is a breaking change. After this patch, the server-side timezone will default to GMT instead of environment
$TZ
. It would be configurable in the future (#2907)Checklist
Refer to a related PR or issue link (optional)
Closes #2856
Part of #2907