Skip to main content

Environment diff tool for dbt

Project description

Recce

install pipy Python downloads license

InfuseAI Discord Invite

Recce is a PR review tool designed for DBT projects. It facilitates the comparison of results between two environments, such as development and production, and helps in identifying any differences.

Features

Use cases

Recce is primarily designed for PR Review purposes. However, it can be expanded to the following use cases:

  1. During development, we can verify new results by contrasting them with those from production prior to pushing the changes.
  2. While reviewing PR, you can grasp the extent of the changes and their impact before merging.
  3. For troubleshooting, you can execute ad-hoc diff queries to pinpoint the root causes.

Usage

Prerequisites

You have to have at least two environments in your dbt project. For example, one is for development and another is for production. You can prepare two targets with separate schemas in your DBT profile. Here is profiles.yml example

jaffle_shop:
  target: dev
  outputs:
    dev:
      type: duckdb
      path: jaffle_shop.duckdb
      schema: dev
    prod:
      type: duckdb
      path: jaffle_shop.duckdb
      schema: main

Getting Started

5 minutes walkthrough by jaffle shop example

  1. Installation

    pip install recce
    
  2. Go to your DBT project

    cd your-dbt-project/
    
  3. Prepare artifacts for base environment in target-base/ folder

    git checkout main
    
    # Generate artifacts for base environment to 'target-base'
    dbt docs generate --target prod --target-path target-base/
    
  4. Prepare artifacts for current working environment

    git checkout feature/my-awesome-feature
    
    # Run dbt and generate artifacts for current working environments
    dbt run
    dbt docs generate
    
  5. Run the recce server.

    recce server
    
    # or with persistent state
    # recce server issue-123.json
    

    Recce would diff environments between target/ and target-base/

Recce use dbt artifacts, which is generated when every invocation. You can find these files in the target/ folder.

artifacts DBT command
manifest.json dbt docs generate, dbt run, ..
catalog.json dbt docs generate

[!TIP] The regeneration of the catalog.json file is not required after every dbt run. it is only required to regenerate this file when models or columns are added or updated.

Lineage Diff

Ad-Hoc Query and Query Diff

You can use any dbt macros installed in your project.

select * from {{ ref("mymodel") }}

In the query diff, which involves comparing the results from two different environments, the browser is required to pull all result data to the client side. Consequently, minimizing the data volume in the query results is essential for efficiency and performance.

[!TIP] Hotkeys Cmd + Enter: Run query Cmd + Shift + Enter: Run query diff

Schema diff

To use schema diff, make sure that both environments have catalog.json.

Row count diff

Profile diff

Profile diff uses the get_profile from dbt_profiler. Make sure that this package is installed in your project.

packages:
  - package: data-mie/dbt_profiler
    version: <version>

Please reference [dbt-profiler] to understand the definition of each profiling stats.

Value diff

  1. Added: New added PKs.
  2. Removed: Removed PKs.
  3. Matched: For a column, the count of matched value of common PKs.
  4. Matched %: For a column, the ratio of matched over common PKs.

PK: Primary key

Value diff uses the compare_column_values from audit-helper. Make sure that this package is installed in your project.

packages:
  - package: dbt-labs/audit_helper
    version: <version>

Value diff requires to select a column as private key. The catalog.json is required to list the available columns.

Checklist

When you feel that your query is worth recording, you can add it to the checklist and name the title and leave a description. This is very helpful for subsequent posting in PR comments.

Q&A

Q: How recce connect to my data warehouse? Does recce support my data warehouse?

recce use the dbt adapter to connect to your warehouse. So it should work for your data warehouse.

Q: What credential does recce connect to the two environments?

Recce uses the same target in the profile to connect your warehouse. If you use the default target dev, it uses the credentials to connect to both environments. So please make sure that the credential can access both environments.

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

recce-nightly-0.8.0.20240225.tar.gz (782.1 kB view details)

Uploaded Source

Built Distribution

recce_nightly-0.8.0.20240225-py3-none-any.whl (796.4 kB view details)

Uploaded Python 3

File details

Details for the file recce-nightly-0.8.0.20240225.tar.gz.

File metadata

  • Download URL: recce-nightly-0.8.0.20240225.tar.gz
  • Upload date:
  • Size: 782.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.0.0 CPython/3.10.13

File hashes

Hashes for recce-nightly-0.8.0.20240225.tar.gz
Algorithm Hash digest
SHA256 50724e2dbc8d0a211980026b326334dea632710891fcec780c1579a793c6ae4e
MD5 2e83cdf222f4e179dce5df1111e53aeb
BLAKE2b-256 31e8cf827ee7fd9f529ca4deb3e32e7199c07d29ff09cf4b9011150d0533d083

See more details on using hashes here.

File details

Details for the file recce_nightly-0.8.0.20240225-py3-none-any.whl.

File metadata

File hashes

Hashes for recce_nightly-0.8.0.20240225-py3-none-any.whl
Algorithm Hash digest
SHA256 1dc6dca1d58b403fea09e6db6c5fa17524d66c722282cdee193218d81ae0ac13
MD5 a477e29c634879ede93894eefab77c88
BLAKE2b-256 944626bca747fce4cbd3cdcf4bd9e99334e7e1670d84a77f560edec706dc5d78

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page