Tracking: dbt Core v2.0 (Fusion) migration for SQL Server

オープン
  • 何か問題がありますか？
#786 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
20/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
静か
技術スタック
python, rust, sql
領域
backend, data-engineering, databases

調査の方向性

This is a tracking issue for a major migration to dbt Core v2.0 (Fusion) for SQL Server. The work is split across multiple repositories and issues. Start by reading the roadmap at https://github.com/dbt-sqlserver-next/dbt-sqlserver-v2-roadmap and the upstream guide at https://docs.getdbt.com/guides/adapter-creation-v2. The implementation work is happening in the fork at dbt-sqlserver-next/dbt-core on the branch sqlserver-v2-port. 'Done' means a complete v2 adapter is merged upstream.

索引モデルが issue の本文から書いたものです。

説明

v2-migration

Tracking: dbt Core v2.0 (Fusion) migration for SQL Server

Summary

Links the issues and PRs — here and in dbt-labs/dbt-core — for bringing SQL Server support to dbt Core v2.0 (the Rust/"Fusion" engine), plus the v1 fixes found while auditing v1 for that port. Decisions and detail live in the roadmap repo plan/; this issue stays a one-line-per-item index.

dbt Labs' Contribute a dbt Core 2.0 Adapter guide has v2 adapters living inside the dbt-core monorepo. v1 (dbt-sqlserver) keeps existing as an independently maintained package; this tracks the parallel v2 work.

Want to help?

  • Align v1 closer to the final v2 state (e.g. #785, #770)
  • Check for bugs or issues on work in progress
Where PRs go
  • Fork: https://github.com/dbt-sqlserver-next/dbt-core
  • Branch: sqlserver-v2-port
  • Open PRs against dbt-sqlserver-next/dbt-core:sqlserver-v2-port, not dbt-labs/dbt-core:main. Rationale: roadmap repo's plan/README.md ("Branching strategy").

Related: aligning v1 with the future v2 parser, on this repo

  • #770 — Explore dbt Core 1.12 v2 parser support: validates the existing Python dbt-sqlserver adapter against dbt Core 1.12's opt-in --use-v2-parser (Rust parser, existing Python adapter — not the Fusion adapter framework this issue tracks). Surfaces project/macro/manifest compatibility issues early, ahead of the full Fusion port below.

dbt-core (v2 adapter implementation)

Granular execution ("Part N" issues, one per crate-scoped unit of work) is tracked on the fork, not here — same reasoning as "Where PRs go" above (Closes #N only works same-repo, and these aren't mergeable upstream yet): dbt-sqlserver-next/dbt-core#1 through #10 (index).

dbt-sqlserver (v1 fixes found while planning the v2 port)

  • #785 — Inconsistent identifier quoting ([bracket] vs "double quote") across a handful of macros
  • (more get added here as they're found/filed)

Deferred / follow-up scope (explicitly out of the v2 initial PR)

Not scheduled — tracked so they aren't lost. Reasoning: roadmap repo's plan/05-open-questions-and-risks.md #4.

  • Dynamic data masking support in v2
  • Index/columnstore materialization config in v2
  • full_refresh_build: prebuilt optimization in v2
  • Scalar function materializations in v2
  • Table clone support in v2
  • Windows/trusted-connection auth in v2

References

主要言語
Python
スター
258
フォーク
112
平均マージ
14時間 6分
マージ済み PR（30日）
10

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

dbt-msft/dbt-sqlserver のほかの issue

dbt-msft/dbt-sqlserver の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。