.jpg%3Falt%3Dmedia%26token%3D220d4374-df04-4938-b958-660d1b7aabef){kind=logo}
.jpg%3Falt%3Dmedia%26token%3D220d4374-df04-4938-b958-660d1b7aabef){kind=logo}
PipeRider
Release notes for PipeRider OSS
Please refer to the PipeRider Releases page on GitHub for more details, including notes on bug fixes and release candidates.
- Support for dry run and interactive mode: The
piperider comparecommand now includes the new options--dry-runand--interactive. - Improvements to the Report UI: Sidebar enhancements including column orders, a modified state indicator, overview item, and hide column nodes for no-profiling models.
- Fixed an issue where the table list displayed incorrect entries.
- Addressed a key error in
compare-reportswhen using the--tables-fromoption. - Resolved an error that occurred when using the
--tableoption in reports.
- dbt test results are now included by default: It's no longer neccessary to use
--dbt-run-results, but it can still be specified without error.
- Bug fixes
Increased focus on dbt project integration.
- It's no longer required to run
piperider initinside dbt projects, just install PipeRider and run - The report sidebar has been redesigned to follow closely with the layout of the dbt docs sidebar, making it easier to navigate for dbt users
- Tracking schema changes: Previously, the profiling was a one-time scan of models with tags, including metadata fetching and execution profiling. Now, in the new version, we have separated the metadata collection and profiling into two distinct phases:
- 1.PipeRider will gather all metadata to track schema changes for models, seeds, and sources.
- 2.PipeRider will continue to profile only those models that have been tagged for profiling.
The following features are now deprecated and will be removed from a future version of PipeRider:
- Using PipeRider in non-dbt projects
- PipeRider assertions
These features are still included in PipeRider for the time being, but are not recommended for continued use.
Bug fix:
- Piperider bug with PipeRider using the wrong schema when using the
--tableoption
Bug fixes, including:
- Fix issue when loading dbt project yaml
- Fix PiperRider Cloud report URL in CLI output
- AWS Athena Support: PipeRider now supports querying and profiling data stored in AWS Athena.
- Skipped model reasons: We have added the ability to display the reason why certain models were skipped during profiling and metric queries, making it easier for users to understand and improve their data pipeline.
- Compare Recipe Enhancements:
- Our Compare recipe has been enhanced to support both file and Jinja formats, allowing users to template values from environment variables for more dynamic comparisons.
- The
comparecommand now supports comparing to a file. This means you can manually set the baseline to an existing report, and then use that in future comparisons without the need to run the baseline profile each time.
- Other Enhancements and Bug Fixes: We have also made several other enhancements and bug fixes, including the addition of buttons for GitHub, Discord, and documentation feedback, ensuring users have an easy and efficient way to provide feedback and suggestions for future improvements.
- We are excited to announce the release of our new Compare GitHub Action! This powerful new feature allows you to easily compare code changes and send summary to your PR comment. For more information, please visit our GitHub Marketplace page.
- We have made some layout adjustments to our application to improve its responsiveness and overall user experience.
- Resolved an issue related to symbolic links on Windows.
- Changed to using 'three-dot compare' (instead of two-dot) when running
piperider compare. Refer to the GitHub documentation for more information on two-dot and three-dot Git diff comparisons.
- Improved the cloud signup process.
piperider comparenow supports PipeRider cloud.
Last modified 1d ago