Exporter/clickhouse support for distributed table

[nengc]

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

[github-actions[bot]]

Pinging code owners:

• exporter/clickhouse: @hanjm @dmitryax @Frapschen @SpencerTorres

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[mshustov]

@SpencerTorres closed by https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/31920?

[nengc]

Hi @mshustov ，i mean the clickhouse sharding using the “Distributed Table”，not the replica

[Frapschen]

@nengc I think cluster_name and table_engine in https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/clickhouseexporter#configuration-options wil achive your goal

[SpencerTorres]

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!

[SpencerTorres]

This can be closed @crobert-1. Users now have full control over table creation with example DDL provided

[crobert-1]

Thanks @SpencerTorres!