Skip to content

dbt Core 2.0 parity: dbt clone support #730

Closed

Description

@koletzilla

Sub-issue of #660. dbt clone (state-based cloning) for the ClickHouse adapter in dbt Core 2.0. The ClickHouse clone macros are merged (dbt-labs/dbt#16750).

Status legend:

  • ✅ implemented — merged and working on dbt-core 2.0 origin/main
  • 🟡 partial — partly working on origin/main; Notes say what works vs fails
  • 🚧 in progress — implemented in an open PR (linked in Notes)
  • 🔴 not started — not working anywhere
Feature What it means Status Notes
dbt clone (overall) ✅ dbt-labs/dbt#16750 (clone.sql)
clone.sql (can_clone_table / create_or_replace_clone) MergeTree tables cloned via CREATE OR REPLACE TABLE … CLONE AS (ON CLUSTER when configured); distributed/non-MergeTree fall back to view; MV target-table cloning ✅ dbt-labs/dbt#16750

Not v1 parity but missing v2 functionality, tracked upstream in dbt-labs/dbt#16589: dbt clone --resource-type / --exclude-resource-type, dbt-core's deferral error wording, and the state-equals-target warning for a relative --state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions