Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Hello Team, We are using clickhouse connector present in airbyte to load the data but it seems the airbyte only supports a single node, do we have any timeline to when we can expect the connector to push the data to a clickhouse cluster. please let me know if i am missing something.

At the moment, the Airbyte ClickHouse destination connector is generally designed around writing to a single ClickHouse endpoint, and native awareness/support for distributed ClickHouse clusters is still limited.

<@U0B3FHSS8K0> , there is a pr someone raised for clickhouse distributed system,  i was hoping to get a timeline on it.

pr link: <https://github.com/airbytehq/airbyte/pull/76945|feat(destination-clickhouse): support Replicated database engine by KadekM · Pull Request #76945 · a…>

Hi Airbyters!

We are currently using `destination-clickhouse` in Airbyte for data loading, but at the moment, it appears to support only a single ClickHouse endpoint. Support for writing directly to a distributed ClickHouse cluster is becoming increasingly important for our use case, and I wanted to follow up on whether there is any expected timeline for this capability.

I also noticed there is already a PR open related to distributed/replicated ClickHouse support: feat(destination-clickhouse): support Replicated database engine by KadekM · PR #76945

Given the growing need for production-grade ClickHouse deployments to operate in clustered/distributed modes, it would be very helpful to understand whether this feature is being prioritized and what the likely path forward looks like. If there is anything the community can do to help move this forward - testing, feedback, or validation - we would be happy to support.
If there is already a recommended workaround or approach for loading into a distributed ClickHouse setup today, I’d also appreciate any guidance.

Thanks!

Hi folks. We're interested in prioritizing this. Before we do so, it would be great to learn a bit more about your specific use case. We haven't tackled clustered ClickHouse setups before so we'd love to know more about why you're doing this and what "production-grade" looks like to you. The extra context is always helpful to make sure we do this right.