Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request to suppress output header when no validations to report #1274

Open
nj1973 opened this issue Sep 19, 2024 · 1 comment
Open
Labels
priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.

Comments

@nj1973
Copy link
Contributor

nj1973 commented Sep 19, 2024

A request from a customer:

"Currently the schema validation outputs blank entries for tables matching (with --filter-status=fail). Is it possible to suppress the table outputs in such cases?"

This would apply to all validation types. The customer is redirecting results to CSV and not storing them in BigQuery.

I've raised this on their behalf but we would need to think carefully about how this might effect other users or general usability.

@nj1973 nj1973 added the type: feature request 'Nice-to-have' improvement, new feature or different behavior or design. label Sep 19, 2024
@nj1973
Copy link
Contributor Author

nj1973 commented Sep 23, 2024

Related to this, another inconvenience around CSV headers is if we validate multiple tables in the same command and redirect the output to a CSV file then we get the header multiple times, part way through the file.

Ideally we would output the CSV header for the first run id and not for subsequent run ids.

@helensilva14 helensilva14 added the priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) label Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants