ClickHouse/dbt-clickhouse v1.10.0

on GitHub

This is an interesting release with many changes! Please take some time to review the notes before upgrading it. All changes are expected to be backward compatible, but some of them may require adjustments in your code.

Changes that specially require your attention

• Respect catchup in materializataion: materialized_view configuration flag during full refresh operations for materialized views. When catchup: False is set, the target table will not be backfilled with historical data during full refresh, providing consistent behavior across initial creation and redeployment scenarios by @dlouseiro in #589
• Add select_sequential_consistency=1 setting for SharedMergeTree (database_engine: Shared) to ensure read-after-write consistency. Shared engine also uses stricter mutations_sync=3 and alter_sync=3 defaults. All connection settings now use setdefault() allowing users to override defaults via custom_settings. Those settings are expected to be safe for all dbt workloads so it's safe in production, but in specific performance critical situations you may want to override it by @koletzilla in #596

Improvements

• Huge new update for Materialized Views! Now you can define which target table will be used. For a full context on how to use it, check the documentation by @koletzilla in #582
• Add in materializataion: dictionary the settings update_field and update_lag, which is used in https://clickhouse.com/docs/sql-reference/dictionaries#refreshing-dictionary-data-using-lifetime and make lifetime optional by @herbert-allium in #580
• Move to declarative packaging to provide better tooling integration and build isolation (by enabling python-build) by @mariocj89 in #593
• Update dbt-adapters version to 1.22 by @koletzilla in #609

Bugs

• Fix incremental models failing with ON CLUSTER when the table exists on a single shard. The can_on_cluster flag now also considers the cluster configuration from the profile, not just the actual shard distribution by @ShimonSte in #599
• Fix issue where AWS credentials used in s3source were not read when defined outside the macro call:
  • Fix for aws_access_key_id and aws_secret_access_key by @ShimonSte in #601
  • Fix for role_arn by @sarahdasko in #440

New Contributors

• @ShimonSte made their first contribution in #599
• @mariocj89 made their first contribution in #593
• @sarahdasko made their first contribution in #440

Full Changelog: v1.9.8...v1.10.0