-
Notifications
You must be signed in to change notification settings - Fork 511
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 option to ignore columns in equality
test
#734
Comments
@joellabes What do you think about moving forward with this? I'd be game to put some work into this in the next couple of weeks! |
@brunocostalopes thanks for this! I am very on board with this as an idea. Some implementation notes:
Since it's your issue and you've got the code already to hand, you get first dibs on implementing it, but if you're not going to have time to do the other things then it looks like @deanna-minnick is also willing to lend a hand - just let us know on the issue thread. Let me know if you run into any issues 🎉 |
@joellabes sounds good, thank you for the implementation notes. I'll take a first stab at it and if it seems like I'm stuck I'll ask @deanna-minnick for a bit of help. |
equality
testequality
test
@joellabes I've raised the PR. Please feel free to comment and suggest any changes, particularly if you have any suggestions on how to compare the list of columns in the ignore list with the list returned by the adapter EDIT: just realised that I was getting the |
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. |
Describe the feature
I would like to be able to specify a list of columns to exclude on an
equality
test.Describe alternatives you've considered
We can of course use
compare_columns
to list all columns, except the ones we want to exclude, but this leads to large yml files, difficult to maintain as our models evolve.Additional context
Not database specific, it can be implemented across all different databases.
Who will this benefit?
This feature would be great for anyone who wants to compare data across environments where, for example, some of the fields are masked in one of the environments.
Another scenario where this can be useful is when updating the logic on a small subset of fields in a model and wanting to compare the development model with the production one, but obviously excluding the updated fields (which are expected to be different)
Are you interested in contributing this feature?
I have implemented this locally already. Happy to raise a PR if people think this feature is helpful.
The text was updated successfully, but these errors were encountered: