-
Notifications
You must be signed in to change notification settings - Fork 34
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
[DC-3352] Fix bug EhrSubmissionDataCutoff.affected_tables is unset #1661
base: develop
Are you sure you want to change the base?
Conversation
Note: Uninitialized affected_tables causes reporter to fail with error getting sandbox table names [DC-3351]
1dcbf59
to
f36632f
Compare
…f.get_affected_tables
f36632f
to
15779a4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @mark-velez! It looks good. I left another solution in the comment. Both ways exist in our code base, so this will be just a matter of preference. This PR is good to close.
Thanks 🎉
tables.append(table) | ||
return tables | ||
sandbox_dataset_id=sandbox_dataset_id, | ||
affected_tables=get_affected_tables()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works. We can also change this line to
affected_tables=[table for table in AOU_REQUIRED if table != 'person']
and remove get_affected_tables()
altogether.
If we do that, patching for the test will be similar to this one: https://github.com/all-of-us/curation/blob/develop/tests/integration_tests/data_steward/cdr_cleaner/cleaning_rules/remove_records_with_wrong_date_test.py#L56
Note: Uninitialized affected_tables causes reporter to fail with error getting sandbox table names DC-3351