-
Notifications
You must be signed in to change notification settings - Fork 334
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
fix: remove to_timezone function #4439
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4439 +/- ##
==========================================
- Coverage 85.03% 84.74% -0.30%
==========================================
Files 1075 1074 -1
Lines 192560 192330 -230
==========================================
- Hits 163750 162991 -759
- Misses 28810 29339 +529 |
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
First, the
to_timezone
function doesn't make sense, because GreptimeDB timestamp types don't contain the timezone info, they are always in theUTC
timezone. The timezone only affects the conversation between timestamps and strings, and we already take care of it.Second, the current implementation of
to_timezone
is incorrect, it's return type is always strings:greptimedb/src/common/function/src/scalars/timestamp/to_timezone.rs
Line 150 in b81d3a2
But the
return_type
depends on the first input type:greptimedb/src/common/function/src/scalars/timestamp/to_timezone.rs
Line 64 in b81d3a2
So let's remove it at all.
Checklist