Project import generated by Copybara.

GitOrigin-RevId: ad7e3349e907abb85fe1d035dc9503e7f2c06ff3

Author: fa-assistant

.changes/README.md

@@ -0,0 +1,52 @@
+# CHANGELOG Automation
+
+We use [changie](https://changie.dev/) to automate `CHANGELOG` generation.  For installation and format/command specifics, see the documentation.
+
+### Quick Tour
+
+- All new change entries get generated under `/.changes/unreleased` as a yaml file
+- `header.tpl.md` contains the contents of the entire CHANGELOG file
+- `.changie.yaml` contains the fields in a change, the format of a single change, as well as the format of the Contributors section for each version.
+
+### Workflow
+
+#### Daily workflow
+Almost every code change we make associated with an issue will require a `CHANGELOG` entry.  After you have created the PR in GitHub, run `changie new` and follow the command prompts to generate a yaml file with your change details.  This only needs to be done once per PR.
+
+The `changie new` command will ensure correct file format and file name.  There is a one to one mapping of issues to changes.  Multiple issues cannot be lumped into a single entry. If you make a mistake, the yaml file may be directly modified and saved as long as the format is preserved.
+
+Note: If your PR has been cleared by the team as not needing a changelog entry, the `Skip Changelog - dbt-fusion` label may be put on the PR to bypass the GitHub action that blacks PRs from being merged when they are missing a `CHANGELOG` entry.
+
+#### Prerelease Workflow
+These commands batch up changes in `/.changes/unreleased` to be included in this prerelease and move those files to a directory named for the release version.  The `--move-dir` will be created if it does not exist and is created in `/.changes`.
+
+```
+changie batch <version>  --move-dir '<version>' --prerelease 'rc1'
+changie merge
+```
+
+Example
+```
+changie batch 1.0.5  --move-dir '1.0.5' --prerelease 'rc1'
+changie merge
+```
+
+#### Final Release Workflow
+These commands batch up changes in `/.changes/unreleased` as well as `/.changes/<version>` to be included in this final release and delete all prereleases.  This rolls all prereleases up into a single final release.  All `yaml` files in `/unreleased` and `<version>` will be deleted at this point.
+
+```
+changie batch <version>  --include '<version>' --remove-prereleases
+changie merge
+```
+
+Example
+```
+changie batch 1.0.5  --include '1.0.5' --remove-prereleases
+changie merge
+```
+
+### A Note on Manual Edits & Gotchas
+- Changie generates markdown files in the `.changes` directory that are parsed together with the `changie merge` command.  Every time `changie merge` is run, it regenerates the entire file.  For this reason, any changes made directly to `CHANGELOG.md` will be overwritten on the next run of `changie merge`.
+- If changes need to be made to the `CHANGELOG.md`, make the changes to the relevant `<version>.md` file located in the `/.changes` directory.  You will then run `changie merge` to regenerate the `CHANGELOG.MD`.
+- Do not run `changie batch` again on released versions.  Our final release workflow deletes all of the yaml files associated with individual changes.  If for some reason modifications to the `CHANGELOG.md` are required after we've generated the final release `CHANGELOG.md`, the modifications need to be done manually to the `<version>.md` file in the `/.changes` directory.
+- changie can modify, create and delete files depending on the command you run.  This is expected.  Be sure to commit everything that has been modified and deleted.

.changes/header.tpl.md

@@ -0,0 +1,7 @@
+# dbt Fusion Changelog
+All notable changes to this project will be documented in this file.
+
+- This file provides a full account of all changes to `dbt-fusion`
+- Changes are listed under the (pre)release in which they first appear. Subsequent releases include changes from previous releases.
+- "Breaking changes" listed under a version may require action from end users or external maintainers when upgrading to that version.
+- Do not edit this file directly. This file is auto-generated using [changie](https://github.com/miniscruff/changie). For details on how to document a change, see [the contributing guide](../CONTRIBUTING.md#adding-a-changelog-entry)

.changes/unreleased/.gitkeep

@@ -0,0 +1,3 @@
+kind: Under the Hood
+body: Bump databricks driver to 0.18.0+dbt0.0.4
+time: 2025-05-30T11:13:15.721996-07:00

.changes/unreleased/Under the Hood-20250530-111315.yaml

@@ -0,0 +1,25 @@
+changesDir: .changes
+unreleasedDir: unreleased
+headerPath: header.tpl.md
+versionHeaderPath: ""
+changelogPath: CHANGELOG.md
+versionExt: md
+versionFormat: '## dbt-fusion {{.Version}} - {{.Time.Format "January 02, 2006"}}'
+kindFormat: "### {{.Kind}}"
+changeFormat: |-
+  - {{.Body}}
+
+kinds:
+  - label: Breaking Changes
+  - label: Features
+  - label: Fixes
+  - label: Under the Hood
+  - label: Dependencies
+  - label: Security
+
+newlines:
+  afterChangelogHeader: 1
+  afterKind: 1
+  afterChangelogVersion: 1
+  beforeKind: 1
+  endOfVersion: 1

.changie.yaml

@@ -0,0 +1,8 @@
+# dbt Fusion Changelog
+All notable changes to this project will be documented in this file.
+
+- This file provides a full account of all changes to `dbt-fusion`
+- Changes are listed under the (pre)release in which they first appear. Subsequent releases include changes from previous releases.
+- "Breaking changes" listed under a version may require action from end users or external maintainers when upgrading to that version.
+- Do not edit this file directly. This file is auto-generated using [changie](https://github.com/miniscruff/changie). For details on how to document a change, see [the contributing guide](../CONTRIBUTING.md#adding-a-changelog-entry)
+

CHANGELOG.md

@@ -33,4 +33,20 @@ Code can be merged into the current development branch main by opening a pull re
 
 Automated tests run via GitHub Actions. If you're a first-time contributor, all tests (including code checks and unit tests) will require a maintainer to approve. Changes in the dbt-fusion repository trigger integration tests against Postgres. dbt Labs also provides CI environments in which to test changes to other adapters, triggered by PRs in those adapters' repositories, as well as periodic maintenance checks of each adapter in concert with the latest dbt-fusion code changes.
 
-Once all tests are passing and your PR has been approved, a dbt-fusion maintainer will merge your changes into the active development branch. And that's it! Happy developing 🎉
+Once all tests are passing and your PR has been approved, a dbt-fusion maintainer will merge your changes into the active development branch. And that's it! Happy developing 🎉
+
+## Adding a CHANGELOG Entry
+
+We use [changie](https://changie.dev) to generate `CHANGELOG` entries. **Note:** Do not edit the `CHANGELOG.md` directly. Your modifications will be lost.
+
+Follow the steps to [install `changie`](https://changie.dev/guide/installation/) for your system.
+
+Once changie is installed and your PR is created for a new feature, simply run the following command and changie will walk you through the process of creating a changelog entry:
+
+```shell
+changie new
+```
+
+Commit the file that's created and your changelog entry is complete!
+
+You don't need to worry about which `dbt-fusion` version your change will go into. Just create the changelog entry with `changie`, and open your PR against the `main` branch. All merged changes will be included in the next release of `dbt-fusion`.  If a changelog is not required, a maintainer can add the label `Skip Changelog - dbt-fusion` to bypass this requirement.

CONTRIBUTING.md

@@ -3,6 +3,7 @@
 members = [
 
   # Source Available
+  "crates/dbt-agate",
   "crates/dbt-common",
   "crates/dbt-frontend-common",
   "crates/dbt-frontend-schemas",
@@ -35,7 +36,7 @@ homepage = "https://getdbt.com"
 keywords = ["sql", "parquet", "json", "csv", "dbt"]
 license = "<>"
 repository = "https://github.com/dbt-labs/dbt-fusion"
-version = "2.0.0-beta.5"
+version = "2.0.0-beta.12"
 
 # We currently need a fork of apache/arrow-datafusion with a few patches.
 # However, note that we declare dependencies in our crates with the same version
@@ -122,6 +123,7 @@ opt-level = 3
 
 # fs source available dependencies
 dbt-adapter-proc-macros = { path = "crates/dbt-adapter-proc-macros" }
+dbt-agate = { path = "crates/dbt-agate" }
 dbt-common = { path = "crates/dbt-common" }
 dbt-dag = { path = "crates/dbt-dag" }
 dbt-deps = { path = "crates/dbt-deps" }
@@ -342,10 +344,15 @@ anyhow = { version = "1.0.74" }
 # logging
 log = { version = "0.4.27", features = ["kv_serde"] }
 
-# tracing
+# tracing (observability)
 tracing = "0.1.41"
 tracing-subscriber = { version = "0.3.19", features = ["env-filter", "json"] }
 
+# tracing (local profiling)
+# Compile with --features "tracy-client/enable" to enable integration with the
+# Tracy profiler: https://github.com/wolfpld/tracy
+tracy-client = { version = "0.18.0", default-features = false }
+
 [workspace.lints.rust]
 # When updating these lints mind that some crates may not inherit form workspace
 # Use only "warn" in this section. CI run will turn these into deny,

Cargo.toml

@@ -1,6 +1,6 @@
-# LICENSES
+# DESCRIPTION 
 
-The `dbt-fusion` repository uses multiple licenses, shown below.
+The dbt Fusion Monorepo uses multiple licenses, shown below.
 
 Unless otherwise specified, every folder and file in this repository is licensed under the Elastic License 2.0 (ELv2).
 
@@ -12,7 +12,7 @@ Unless otherwise specified, every folder and file in this repository is licensed
 
 
 ---
-# Elastic License 2.0
+Elastic License 2.0
 
 ## Acceptance
 
@@ -295,7 +295,7 @@ these terms.
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright 2025 dbt Labs, Inc.
+   Copyright 2019 Elastic and contributors
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

LICENSES.md

@@ -8,34 +8,34 @@
 
 This repo hosts components of the dbt Fusion engine, the foundation for future innovation in `dbt`. The dbt Fusion engine is written in Rust and is designed for speed, correctness, and has a native understanding of SQL across multiple data warehouse SQL dialects.
 
-> [!IMPORTANT]
+> [!IMPORTANT]  
 > **Note: the dbt Fusion Engine is in Beta!**
-Bugs and missing functionality compared to dbt Core will be resolved continuously in the lead-up to a final release (see [this post](https://docs.getdbt.com/blog/dbt-fusion-engine-path-to-ga) for more details).
+Bugs and missing functionality compared to dbt Core will be resolved continuously in the leadup to a final release (see [this post](https://docs.getdbt.com/blog/fusion-path-to-ga) for more details). 
 
-The dbt Fusion engine is a ground-up, first principles rewrite of the dbt Core execution engine, built to be interoperable with the standard dbt authoring layer. Fusion enforces some ambiguous areas of the authoring spec more strictly than dbt Core to ensure correctness (for example, dbt Core does not proactively validate most YAML configurations). Many of these discrepancies can be fixed automatically with the [dbt Autofix](https://github.com/dbt-labs/dbt-autofix) tool.
+The dbt Fusion engine is a ground up, first principles rewrite of the dbt Core execution engine, built to be interoperable with the standard dbt authoring layer. Fusion enforces some ambiguous areas of the authoring spec more strictly than dbt Core to ensure correctness (for example, dbt Core does not proactively validate most YAML configurations). Many of these discrepancies can be fixed automatically with the [dbt Autofix](https://github.com/dbt-labs/dbt-autofix) tool.
 
 Beyond conformance with dbt Core, Fusion also contains new SQL Comprehension capabilities, a language server, modern ADBC drivers for warehouse connections, and more. While dbt Core was written in Python, the dbt Fusion engine is written in Rust, and compiled to a single application binary.
 
-You can install dbt-fusion onto your local machine, a docker container, or a machine in the cloud. It is designed for flexible installation, with no dependencies on other libraries. The only libraries that dbt Fusion will load are its corresponding database drivers.
+You can install dbt-fusion onto your local machine, a docker container, or a machine in the cloud. It is designed for flexible installation, with no dependencies on other libraries. The only libraries that dbt Fusion will load are it's corresponding database drivers.
 
 The dbt Fusion engine is being released to this repository incrementally, so, until this note is removed this repository contains only a subset of the crates that make the core of the engine work. These crates are published incrementally starting on May 28.
 
 ## Getting Started with the dbt Fusion engine
 
-> [!TIP]
-> You don't have to build this project from source to use the new dbt! We recommend using the precompiled binary with additional capabilities:
+> [!TIP]  
+> You don't have to build this project from source to use the new dbt! We recommend using the precompiled binary with additional capabilities: 
 
-There are several ways to get started with Fusion (for more, see dbt Fusion's quickstart documentation [here](https://docs.getdbt.com/guides/fusion?step=1)):
-1. **Download the dbt VS Code extension** - For most people the best experience. This will install the dbt fusion CLI and Language Server on your system - see the install guide [here](https://docs.getdbt.com/docs/install-dbt-extension).
-2. **Install Fusion Directly** - Install just the fusion CLI with the command below or see dbt's documentation [here](https://docs.getdbt.com/docs/fusion/install-fusion)
+There are several ways to get started with Fusion (for more, see dbt Fusion's quickstart documentation [here](https://docs.getdbt.com/guides/fusion?step=1))
+1. **Download dbt the vs-code extension** - For most people the best experience. This will install the dbt fusion CLI and Language Server on your system - see the install guide [here](https://docs.getdbt.com/docs/install-dbt-extension).
+2. **Install Fusion Directly** Install just the fusion CLI with the command below or see dbt's documentation [here](https://docs.getdbt.com/docs/fusion/install-fusion)
 ``` bash
 curl -fsSL https://public.cdn.getdbt.com/fs/install/install.sh | sh -s -- --update
 ```
 3. **Build Fusion from Source** - See the *Compiling from Source* section below
 
 
 ### Supported Operating Systems and CPU Microarchitectures
-Fusion & associated drivers are compiled for each CPU microarchitecture and operating system independently. This allows for hardware-level optimization.
+Fusion & associated drivers are compiled for each CPU microarchitecture and operating system independently. This allows for hardware level optimization.
 
 Legend:
 * 🟢 - Supported today
@@ -62,12 +62,12 @@ Legend:
 ### Top Level Components Released to Date
 Releases of various Fusion components will be iterative as each component reaches maturity & readiness for contribution.
 
-- [x] `dbt-jinja` - A Rust extension of mini-jinja to support dbt's jinja functions & other capabilities
+- [x] `dbt-jinja` - All Rust extension of mini-jinja to support dbt's jinja functions & other capabilities
 - [x] `dbt-parser` - Rust parser for dbt projects
 - [x] `dbt-snowflake` - database driver
 - [x] `dbt-schemas` - complete, correct, machine generated json schemas for dbt's authoring surface
 - [ ] `dbt-sql` - ANTLR grammars and generated parsers
-  - [ ] snowflake.g4
+  - [ ] snowflake.g4 
   - [ ] bigquery.g4
   - [ ] redshift.g4
   - [ ] databricks.g4
@@ -76,33 +76,31 @@ Releases of various Fusion components will be iterative as each component reache
 ## FAQ
 
 <details>
-  <summary><i>Can I contribute to the dbt Fusion engine?</i></summary>
+  <summary><i>Can I con contribute to the dbt Fusion engine?</i></summary>
 
-  Yes, absolutely! Please see our contribution guidelines [here](CONTRIBUTING.md)
+  Yes absolutely!. Please see our contribution guidelines [here](CONTRIBUTING.md)
 </details>
 
 <details>
   <summary><i>How is dbt Fusion different from dbt Core?</i></summary>
-
   The dbt Fusion engine is a ground-up rewrite of dbt Core, with many additional capabilities.
-
   *Things that are the same:*
   * The YML authoring format including profiles, configuration, seeds, data tests, and unit tests
   * The materialization libraries
-  * dbt's library management system (although `dbt deps` are installed automatically)
+  * dbt's library managemenet system (although `dbt deps` are installed automatically)
 
   *Additional capabilities provided by Fusion:*
   * All new Arrow Database Connector (ADBC) drivers for faster data transfers and unified connection handling
   * A language server and corresponding VS-Code extension (compatible with Cursor) for ease of development
   * Multi-dialect SQL compilation, validation, & static analysis
-  * Standalone distribution. No JVM, or Python required.
+  * Standalone distribution. No JVM, or python required. 
   * Automatic installation of dependencies, whether that's a dbt package, or database driver
   * dbt code-signed & secure distributions
 </details>
 
 <details>
   <summary><i>This repo doesn't have all of dbt's functionality, when will the rest come?</i></summary>
-  dbt Fusion's source code is being published as components are finalized. Please see the Timeline section above.
+  dbt Fusion's source code is being published as components are finalized. Please see the Timeline section above
 </details>
 
 <details>
@@ -119,7 +117,7 @@ Releases of various Fusion components will be iterative as each component reache
 
 ## Compiling from Source
 
-The primary CLI in this repository is the `dbt-sa-cli`. To compile the CLI, you need the Rust toolchain.
+The primary CLI in this repository is the `dbt-sa-cli`. To compile the CLI, you need the Rust toolchain. 
 
 Let's start with Rust, run the following command to install Rust on your machine:
 
@@ -153,9 +151,9 @@ Options:
 ...
 ```
 
-Cargo is Rust's build system and package manager. If you're familiar with Python, pip would be a sufficient comparison. We'll use cargo to run commands to build the local `dbt-sa-cli` binary and run helper scripts via `cargo xtask`. More on that later.
+Cargo is Rust's build system and package manager. If you're familiar with Python, pip would be a sufficient comparison. We'll use cargo to run command to build the local `dbt-sa-cli` binary and run helper scripts via `cargo xtask`. More on that later.
 
-To build the binary locally, `cd` to this repo's directory and run:
+To build the binary locally, `cd` to the this repo's directory and run:
 
 ```shell
 cargo build
@@ -190,14 +188,14 @@ cd target/debug && pwd
 To run tests, increase the stack size and use nextest.
 
 ```
-RUST_MIN_STACK=8388608 cargo nextest run --no-fail-fast
+ RUST_MIN_STACK=8388608 cargo nextest run --no-fail-fast
 ```
 
 # License
-The dbt Fusion engine is a monorepo and contains more than one license. Most code is licensed under ELv2. For more, please see our [licenses](LICENSES.md) section.
+The dbt Fusion engine is a monorepo and contains more than one License. Most code is licensed under ELv2. For more, please see our [licenses](LICENSES.md) section.
 
 # Acknowledgments
-*To the dbt community:* dbt the tool & dbt Labs the company would not be here without the incredible community of authors, contributors, practitioners, and enthusiasts. dbt Fusion is an evolution of that work & stands on the shoulders of what has come before.
+*To the dbt community:* dbt the tool & dbt Labs the company would not be here without the incredible community of authors, contributors, practitioners, and enthusiasts. dbt Fusion is an evolution of that work & stands on the shoulders of what has come before. 
 
 *To the Arrow Community:* dbt Labs is committing fully to the Arrow ecosystem. Fusion exclusively uses the Arrow type system from drivers through adapters into the internals of the compiler & runtime.