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: administration functions #3236
feat: administration functions #3236
Conversation
2cd56fe
to
1485e2e
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #3236 +/- ##
==========================================
- Coverage 85.63% 85.06% -0.58%
==========================================
Files 859 871 +12
Lines 140515 141479 +964
==========================================
+ Hits 120333 120344 +11
- Misses 20182 21135 +953 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW, I'm not sure whether we should put truncate
in the DDL procedure. Maybe we can refactor it in the future PRs. See also: #2968
Co-authored-by: Weny Xu <wenymedia@gmail.com>
Co-authored-by: Weny Xu <wenymedia@gmail.com>
Co-authored-by: JeremyHi <jiachun_feng@proton.me>
Co-authored-by: fys <40801205+fengys1996@users.noreply.github.com>
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Try to implement some administration functions:
database()
to get the current database.timezone()
to get the current session timezone.FunctionState
for SQL functions to access table or meta service.procedure_state(pid)
andmigrate_region(region, from, to, timeout)
etc. I'll implement them in the following PR.Depends on GreptimeTeam/greptime-proto#137
Checklist
Refer to a related PR or issue link (optional)