Closed qrtt1 closed 1 year ago
Merging #808 (78b4b04) into main (49bbe76) will increase coverage by
0.06%
. The diff coverage is60.86%
.
@@ Coverage Diff @@
## main #808 +/- ##
==========================================
+ Coverage 36.34% 36.41% +0.06%
==========================================
Files 68 68
Lines 9844 9879 +35
==========================================
+ Hits 3578 3597 +19
- Misses 6266 6282 +16
Files Changed | Coverage Δ | |
---|---|---|
piperider_cli/cloud/__init__.py | 0.00% <0.00%> (ø) |
|
piperider_cli/runner.py | 20.27% <0.00%> (-0.15%) |
:arrow_down: |
piperider_cli/profiler/profiler.py | 74.12% <66.66%> (-0.40%) |
:arrow_down: |
piperider_cli/dbt/utils.py | 91.09% <85.00%> (-1.13%) |
:arrow_down: |
piperider_cli/dbt/changeset.py | 90.96% <100.00%> (ø) |
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
Sample for the new profiling data:
Found the output can not pass the schema validator:
Broken data has been fixed.
PR checklist
What type of PR is this?
bugfix
What this PR does / why we need it:
In a real case, users might use the same name for different dbt nodes.
For example:
transaction
in the sourcestransaction
in the seedtransaction
in the modeldefinetransaction
in the staging modelWhich issue(s) this PR fixes:
sc-31825
To Reviewers:
There are two parts in the main goal
[x] error handling in the report generator
[x] fix the profiling output (
run.json
)The first, even if we lost data in
run.json
must not break the report-generating process. A weird one is better than nothing.Except if the data is unavailable, we need to put any table with the same name (e.g.
transaction
) to the profiling results.Ref data for broken report
campaign_transaction
totransaction
, it will conflict withsources.cy.transaction
models/transaction.sql
is not present in therun.json
(thetarget
part from the comparison data)Comparison Summary
Models
26nanMetrics
No changes detected