-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Exporter/clickhouse support for distributed table #32736
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@SpencerTorres closed by #31920? |
Hi @mshustov ,i mean the clickhouse sharding using the “Distributed Table”,not the replica |
@nengc I think |
Please see this response. The other comment is also a good suggestion if you want to use the existing config options, but for now this can be handled by manually creating the table. By manually creating the table you will have full control over these settings. We can close this issue for now. Thanks! |
This can be closed @crobert-1. Users now have full control over table creation with example DDL provided |
Thanks @SpencerTorres! |
Component(s)
exporter/clickhouse
Is your feature request related to a problem? Please describe.
I cannot find anything about the distributed table in the codes. So cannot support sharding at this moment?
https://clickhouse.com/docs/en/engines/table-engines/special/distributed
Describe the solution you'd like
Support distributed table like below:
CREATE TABLE [IF NOT EXISTS] [db.]table_name [ON CLUSTER cluster]
(
name1 [type1] [DEFAULT|MATERIALIZED|ALIAS expr1],
name2 [type2] [DEFAULT|MATERIALIZED|ALIAS expr2],
...
) ENGINE = Distributed(cluster, database, table[, sharding_key[, policy_name]])
[SETTINGS name=value, ...]
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: