-
Notifications
You must be signed in to change notification settings - Fork 300
-
Notifications
You must be signed in to change notification settings - Fork 300
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
information_schema improvements #2931
Labels
C-user-experience
Category User Experience
good first issue
Good for newcomers
help wanted
Extra attention is needed
tracking-issue
A tracking issue for a feature.
Milestone
Comments
killme2008
added
help wanted
Extra attention is needed
tracking-issue
A tracking issue for a feature.
Size: XL
good first issue
Good for newcomers
C-user-experience
Category User Experience
labels
Dec 14, 2023
This was referenced Dec 15, 2023
This was referenced Dec 27, 2023
This was referenced Dec 29, 2023
This was referenced Jan 4, 2024
3 tasks
3 tasks
3 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-user-experience
Category User Experience
good first issue
Good for newcomers
help wanted
Extra attention is needed
tracking-issue
A tracking issue for a feature.
What type of enhancement is this?
API improvement, Configuration, User experience, Other
What does the enhancement do?
Information Schema provides an ANSI-standard way of viewing system metadata. But we only have two internal tables:
tables
andcolumns
, that's not enough for compatibility or such as query functions in #2921 .TiDB has a great doc that describes its information schema: https://docs.pingcap.com/tidb/stable/information-schema
Tasks
So I created this tracking issue to add more tables into
information_schema
and welcome all developers who are interested in GreptimeDB to contribute:utf-8
, so we can just return one row.COLUMN_PRIVILEGES
, not implemented.COLUMN_STATISTICS
, not implemented.mito
,file
engines etc.EVENTS
not implemented.FILES
not implemented. feat: add information_schema.files #3054GLOBAL_STATUS
not implemented.GLOBAL_VARIABLES
not implemented. An idea is that we keep all configurations in this table.OPTIMIZER_TRACE
not implemented.PARAMETERS
not implemented.PROFILING
not implemented.REFERENTIAL_CONSTRAINTS
, we don't support it, returns zero rows instead.ROUTINES
not implemented.SCHEMA_PRIVILEGES
not implemented.SESSION_STATUS
not implemented.TABLESPACES
not implemented.TABLE_PRIVILEGES
not implemented.TRIGGERS
, we don't support it.All the tables that are not implemented, we can just return zero rows.
Of course, we will have some extension tables:
cluster_info
to provide the current cluster info, such as topology etc. feat: adds information_schema cluster_info table #3832build_info
to provide the database build info. build() function to return the database build info #2909slow_query
to record all slow queries.region_peers
to provide region route info. feat: impl partitions and region_peers information schema #3278runtime_metrics
to retrieve the greptimedb runtime metrics feat: adds runtime_metrics #3127The following tasks:
Reference info
Someone who are interested in contributing can refer to these PRs:
#2969
#2935
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: