Manav Paneliya
01/03/2024, 10:01 PMWilli
01/05/2024, 7:41 AMManav Paneliya
01/05/2024, 2:42 PMWilli
01/05/2024, 3:58 PMManav Paneliya
01/05/2024, 4:00 PMjoshuah.kapilivsky
01/05/2024, 4:25 PMnot_null test on this field?
I’m guessing it looks something like
SELECT email
FROM {{ table }}
WHERE email IS NULL
I think if the test were written like this
SELECT *
FROM {{ table }}
WHERE email IS NULL
Then in elementary you would see all the columns for the failing rows.
I’m not an elementary dev, but based on my experience the test previews in the elementary report show the same columns as the stored test failures table in my data warehouse. So you may need to modify the test definition to alter what is seen in the report. Good luck!Manav Paneliya
01/05/2024, 4:28 PMjoshuah.kapilivsky
01/05/2024, 4:58 PMManav Paneliya
01/05/2024, 5:44 PMjoshuah.kapilivsky
01/05/2024, 8:02 PMOfek Weiss
01/08/2024, 2:27 PMyml file, i would like to see how you set it up 😄Manav Paneliya
01/08/2024, 2:31 PMOfek Weiss
01/08/2024, 2:42 PMmeta.description property in those tests.
if, for example, you want to add it to the test dim_order_item_unique_id, then it should look like so:
- name: stg_inventory
columns:
- name: inventory_id
# Unique Tests
tests:
- unique:
alias: dim_order_item_unique_id
meta:
description: "This is a very cool test:)"Manav Paneliya
01/08/2024, 3:12 PMOfek Weiss
01/08/2024, 3:16 PMManav Paneliya
01/08/2024, 3:26 PMOfek Weiss
01/08/2024, 3:31 PMManav Paneliya
01/08/2024, 3:33 PM