We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Allow user to specify the table engine type, e.g.,
CREATE EXTERNAL TABLE external_monitor ( host_id INT, idc STRING, ts TIMESTAMP TIME INDEX, cpu DOUBLE DEFAULT 0, memory DOUBLE, PRIMARY KEY (host), ) ENGINE=file ...
CREATE TABLE my_metric ( host_id INT, idc STRING, ts TIMESTAMP TIME INDEX, cpu DOUBLE DEFAULT 0, memory DOUBLE, PRIMARY KEY (host), ) ENGINE=metric
By default, If we run the following SQL, the database will create a table using a default mito engine.
mito
CREATE TABLE monitor ( host_id INT, idc STRING, ts TIMESTAMP TIME INDEX, cpu DOUBLE DEFAULT 0, memory DOUBLE, PRIMARY KEY (host), )
Which equals the following:
CREATE TABLE monitor ( host_id INT, idc STRING, ts TIMESTAMP TIME INDEX, cpu DOUBLE DEFAULT 0, memory DOUBLE, PRIMARY KEY (host), ) ENGINE=mito
Now, we will support multiple table engines, e.g., file table engine, metric engine, etc.
Some places need to be modified to adapt to this feature.
Registers table engine type to catalog, and removes hard code:
greptimedb/src/catalog/src/tables.rs
Lines 82 to 90 in 0943079
Distinguishes between different table engines via catalog and recovers them:
greptimedb/src/catalog/src/local/manager.rs
Lines 235 to 261 in 0943079
compatibility
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What problem does the new feature solve?
Allow user to specify the table engine type, e.g.,
What does the feature do?
By default, If we run the following SQL, the database will create a table using a default
mito
engine.Which equals the following:
Now, we will support multiple table engines, e.g., file table engine, metric engine, etc.
Some places need to be modified to adapt to this feature.
Registers table engine type to catalog, and removes hard code:
greptimedb/src/catalog/src/tables.rs
Lines 82 to 90 in 0943079
Distinguishes between different table engines via catalog and recovers them:
greptimedb/src/catalog/src/local/manager.rs
Lines 235 to 261 in 0943079
Implementation challenges
compatibility
The text was updated successfully, but these errors were encountered: