-
Notifications
You must be signed in to change notification settings - Fork 75
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
feature: External Table ( for ClickHouse ) #546
Conversation
Hi @zliang-min , please test the behavior of connecting to a view or materialized view in ClickHouse. Probably Proton can still read it but cannot write to it. If the user creates an external table connecting to a ClickHouse view, then try to use it as target for Proton Materialized view. The materialized view DDL should fail, instead of creation is done but no result while MV is running |
Checked, it works for views and materialized views (read-only of course). |
1732614
to
52891b3
Compare
(Jove Github Bot) added it to the current sprint. |
(Jove Github Bot) moved this ticket out of the GitHub project(up to 1200 tickets for one project). |
PR checklist:
proton: starts/ends
for new code in existing community code base ?Please write user-readable short description of the changes:
New feature for creating External Tabels to connect to non-streaming data sources. In this first implementation, a ClickHouse External Table has been implemented.
Examples:
To create an external table:
External tables do not accept the column list, it fetches its table structure from the remote data source. After the table is created, one can use
DESCRIBE my_table
to see its structure.Then, it can be queried just like any tables/streams:
To drop an external table: