Tom Baeyens
Tom Baeyens
Investigate error messages ``` Not executing query adventure_works_human_resources.reference[departmentid] because no sampler is configured. Metrics "reference" were not computed for check values in departmentid must exist in DEPARTMENT departmentid ```
@mathissedestrooper or Benjamin should review the check names as generated by Soda Core. By default, check names are the main check line. For metric checks having nested threshold level specification:...
Remove these logs. ``` | Starting new HTTPS connection (1): collect.soda.io:443 | [https://collect.soda.io:443](https://collect.soda.io/) "POST /v1/traces HTTP/1.1" 200 0 ``` https://sodadata.slack.com/archives/C02J6Q493PY/p1650673735626059
Eg (from Rob's feedback) ``` table_xyz [yesterday]: description: Check data quality for yesterday's surveys filter: where date = current_date - 1 ```
Please review these assumptions first: You have build a docker container to run a scan. In production, the docker container uses a BigQuery service account to run the scan. Developers...
It seems that through the BigQuery command line, it's possible to add labels to jobs / queries: https://cloud.google.com/bigquery/docs/adding-labels#adding_a_label_to_a_job What I didn't find yet is how to set those labels through...
Let's start with a description of how I understood the request for filters as a variable. In SodaCL, you already can define filters: ``` filter CUSTOMERS [daily]: where: TIMESTAMP '${ts_start}'...
Here I provide a list of use cases related to group by. Note that some of these are already available, while for other use cases we are still collecting requirements....
You mentioned that for the time being you don't want to send anything to Soda Cloud, not the samples and not the failed rows. First question that came up for...