What is the motivation behind ending normalization support for Clickhouse? Is the user base too small from a business perspective? This change will essentially rule out Airbyte from our evaluation of tools, so just wanted to get some clarification.

No, in summary normalization module will be replaced by Destination V2 https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2/#what-is-destinations-v2

right, but it appears to be planned to not move Clickhouse to this system: https://github.com/airbytehq/airbyte/issues/32528

Correct. The usage of the feature at the moment is too small for clickhouse to migrate. We will destinations v2 once more clickhouse users ask for it. That said, if you add a tool like dbt, you can accomplish many of the same jobs - typecasting, deduplication, etc. cc @Joe Bell (Airbyte)

thanks for the replies! I noticed @Joe Bell (Airbyte) mentioned dbt cloud in the ticket, but I’m sort of green on all of this so wasn’t sure at which points I could integrate, so I appreciate the info. also.. please consider this another vote for Clickhouse Destination V2 support 😄