[!IMPORTANT] PipeRider has been superseded by Recce. We recommend that users requiring pre-merge data validation checks migrate to Recce. PipeRider will not longer be updated on a regular basis. You are still welcome to open a PR with bug fixes or feature requests. For questions and help regarding this update, please contact product@piperider.io or leave a message in the Recce Discord.
Code review for data in dbt
PipeRider automatically compares your data to highlight the difference in impacted downstream dbt models so you can merge your Pull Requests with confidence.
How it works:
- Easy to connect your datasource -> PipeRider leverages the connection profiles in your dbt project to connect to the data warehouse
- Generate profiling statistics of your models to get a high-level overview of your data
- Compare target branch changes with the main branch in a HTML report
- Post a quick summary of the data changes to your PR, so others can be confident too
Core concepts
- Easy to install: Leveraging dbt's configuration settings, PipeRider can be installed within 2 minutes
- Fast comparison: by collecting profiling statistics (e.g. uniqueness, averages, quantiles, histogram) and metric queries, comparing downstream data impact takes little time, speeding up your team's review time
- Valuable insights: various profiling statistics displayed in the HTML report give fast insights into your data
Quickstart
-
Install PipeRider
pip install piperider[<connector>]
You can find all supported data source connectors here.
-
Add PipeRider tag on your model: Go to your dbt project, and add the PipeRider tag on the model you want to profile.
--models/staging/stg_customers.sql {{ config( tags=["piperider"] ) }} select ...
and show the models would be run by piperider
dbt list -s tag:piperider --resource-type model -
Run PipeRider
piperider run
To see the full quick start guide, please refer to PipeRider documentation
Features
- Model profiling: PipeRider can profile your dbt models and obtain information such as basic data composition, quantiles, histograms, text length, top categories, and more.
- Metric queries: PipeRider can integrate with dbt metrics and present the time-series data of metrics in the report.
- HTML report: PipeRider generates a static HTML report each time it runs, which can be viewed locally or shared.
- Report comparison: You can compare two previously generated reports or use a single command to compare the differences between the current branch and the main branch. The latter is designed specifically for code review scenarios. In our pull requests on GitHub, we not only want to know which files have been changed, but also the impact of these changes on the data. PipeRider can easily generate comparison reports with a single command to provide this information.
- CI integration: The key to CI is automation, and in the code review process, automating this workflow is even more meaningful. PipeRider can easily integrate into your CI process. When new commits are pushed to your PR branch, reports can be automatically generated to provide reviewers with more confidence in the changes made when reviewing.
Example Report Demo
We use the example project git-repo-analytics to demonstrate how to use piperider+dbt+duckdb to analyze dbt-core repository. Here is the generated result (daily update)
PipeRider Cloud (beta)
PipeRider Cloud allows you to upload reports and share them with your team members. For information on pricing plans, please refer to the pricing page.
PipeRider Compare Action
PipeRider provides the PipeRider Compare Action to quickly integrate into your Github Actions workflow. It has the following features:
- Automatically generates a report comparing the PR branch to the main branch
- Uploads the report to GitHub artifacts or PipeRider cloud
- Adds a comment to the pull request with a comparison summary and a link to the report.
You can refer to example workflow yaml and the example pull request.
Development
See setup dev environment and the contributing guildlines to get started.
We love chatting with our users! Let us know if you have any questions, feedback, or need help trying out PipeRider! :heart:
1 maintainer
Metadata
1 maintainer
Release files for piperider-nightly 0.42.0.20240827
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| piperider_nightly-0.42.0.20240827.tar.gz | 4.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| piperider_nightly-0.42.0.20240827-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.3 MB
Release files / piperider_nightly-0.42.0.20240827.tar.gz
| Download URL | piperider_nightly-0.42.0.20240827.tar.gz |
|---|---|
| Size | 4.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
48c6dc1ba07288293e4fc3e5bab79e66e02f6ec7330d8b0b4959da22babda393
|
|
BLAKE2b-256 checksum How to use checksums |
868fc4361421f4c8f611c337ffec1dbb4aa5d4f913f8466523f3d0bef714aecb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.18
|
Release files / piperider_nightly-0.42.0.20240827-py3-none-any.whl
| Download URL | piperider_nightly-0.42.0.20240827-py3-none-any.whl |
|---|---|
| Size | 4.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5cf08efe24bfb24019df5a46e3b009a4057146834de2c4b340b01869f78a9272
|
|
BLAKE2b-256 checksum How to use checksums |
7a91c0531c7de7b76f0e8fb7eedecb04d77699a4884b4614c63837e15956987e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.8.18
|
