-
Notifications
You must be signed in to change notification settings - Fork 503
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
Add optional exclude_columns
to the equality
test
#828
Comments
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers. |
Hi @dbeatty10 , thank you for re-opening this PR. However I think it can be closed, given that this other PR was merged. |
Describe the feature
It'd be nice to have an optional
exclude_columns
in theequality
test, similar tocompare_columns
:Such columns would be ignored when comparing the two tables.
Describe alternatives you've considered
compare_relations
from dbt-audit-helperI don't think either solution is great compared to adding the feature here.
Additional context / Who will this benefit?
As an example, here's why my team would like this. We leverage the
equality
test from dbt-utils to implement unit tests. However, we need to exclude the "processing timestamp" column, as it cannot be predicted for the "expected output" model.Are you interested in contributing this feature?
Yep! In fact, I wrote the PR (#829 ) before the issue, because I'd forgotten that all PRs must be associated with an issue, oops.
The text was updated successfully, but these errors were encountered: