You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to monitor some row counts on my table. I'm planning to set up row count tests and enable storing failures.
I plan to do this with multiple different conditions. I actually expect some of these two fail. The aim is to monitor how badly they fail. The idea is to visualise the outcome in a calendar heat map, to give me a visual on when the issues are big.
I could use the row count test, configured like this:
with grouped_expression as (
select
created_date as col_1,
count(*) =0as expression
fromschema_name.table_namewhere
some_column='failed'group by created_date
),
validation_errors as (
select*from
grouped_expression
where
not(expression = true)
)
select*from validation_errors
I wish the compiled code would have an additional column for the actual row_count, like this:
Sample compiled code:
with grouped_expression as (
select
created_date as col_1,
count(*) as row_count,
count(*) =0as expression
fromschema_name.table_namewhere
some_column='failed'group by created_date
),
validation_errors as (
select*from
grouped_expression
where
not(expression = true)
)
select*from validation_errors
to return
It's not a breaking change as the logic of the test remains the same. We're just making the stored output more informative.
I'm happy to contribute, but I could not immediately figure out where to make this change. The actual code compiling happens through so many macros that I'm not (yet) familiar with.
The text was updated successfully, but these errors were encountered:
I want to monitor some row counts on my table. I'm planning to set up row count tests and enable storing failures.
I plan to do this with multiple different conditions. I actually expect some of these two fail. The aim is to monitor how badly they fail. The idea is to visualise the outcome in a calendar heat map, to give me a visual on when the issues are big.
I could use the row count test, configured like this:
However, the outcome is a true/false only.
Sample compiled code:
I wish the compiled code would have an additional column for the actual row_count, like this:
Sample compiled code:
to return
It's not a breaking change as the logic of the test remains the same. We're just making the stored output more informative.
I'm happy to contribute, but I could not immediately figure out where to make this change. The actual code compiling happens through so many macros that I'm not (yet) familiar with.
The text was updated successfully, but these errors were encountered: