Josh Andrews

Just looking over the issues list here... One possibility for this might be to piggyback on dbt-expectations? There are some tests already like this: https://github.com/calogica/dbt-expectations#expect_column_to_exist and https://github.com/calogica/dbt-expectations#expect_table_columns_to_contain_set

Thanks @dbeatty10 much appreciated!

Hi @jtcohen6 Happy New Year to you as well, and thanks for the as-always in-depth response! So I did some digging into BigQuery `INFORMATION_SCHEMA` and job history. It turns out...

Another possible related thought on this. What if the table into which test results are stored actually became a node in the DAG? Given that tests are already nodes in...

I'm going to try using on-run-end post-hook combined with a macro, and then we also just got JSON support enabled for our BQ environment today (it's a special thing that...

So I did this initial take for BigQuery, basing off of code in this issue (which was for Snowflake): https://github.com/dbt-labs/dbt-core/issues/4099: ``` {% macro centralize_test_failures(results) %} {%- set test_results = []...

Some additional thoughts/failure modes/concerns to think about with this: 1. In large dbt projects, one problem with project-wide variables is the potential for developers to "step" on each other by...

Thanks for the compliment on the username @jtcohen6 :). I think a `vars.yml` file would be a definite improvement over the current situation. Would it be required or could vars...

Just looking through issue backlogs and wanted to bump this... Would be great as we are working with projects that have tens or even hundreds of variables now. Also the...

I want this feature as much as anyone, and having said that, I'm not so sure that the data in the schema.yml files provides the full information needed to do...