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.9.0.20240312.tar.gz (816.1 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

recce_nightly-0.9.0.20240312-py3-none-any.whl (831.3 kB view details)

Uploaded Python 3

File details

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

File metadata

  • Download URL: recce-nightly-0.9.0.20240312.tar.gz
  • Upload date:
  • Size: 816.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.9.0.20240312.tar.gz
Algorithm Hash digest
SHA256 6c42e81e4d5b75e6718b40ddb7c8d3dbff37ab55ae6a16ed1570bc78b3d07b82
MD5 a159e4ec8f14a514636f04559e816864
BLAKE2b-256 c68ccde0615abf888d0ccade0e1fc90482c4c402fedef38bf8fb00d1202e6ad2

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for recce_nightly-0.9.0.20240312-py3-none-any.whl
Algorithm Hash digest
SHA256 27387b2eb2b1d5a464cb83a7d225898298b32e0bc0f1ee284e399958fee982e2
MD5 73c280354657d9ec3b7973fed6181af7
BLAKE2b-256 7f36b72d45122423ee95dc0fea2365cf312d534f4ac13174bca83e6cc3f07809

See more details on using hashes here.

Supported by

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