-
Notifications
You must be signed in to change notification settings - Fork 112
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
feat: Support config directory for running validations and add multithreading for DB queries #654
Conversation
dmedora
commented
Dec 22, 2022
•
edited
Loading
edited
- Adds support for specifying a directory to run validation yamls from (either local or GCS).
- Adds multithreading to source & target database query requests, so these happen simultaneously, effectively halving total time waiting for external query execution.
…e build_config_managers_from_yaml; functions for --config-file as before, --config-dir in progress.
/gcbrun |
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.
Looks perfect!
|
||
def build_config_managers_from_yaml(args, config_file_path): | ||
"""Returns List[ConfigManager] instances ready to be executed.""" | ||
if "config_dir" in args and args.config_dir: |
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.
Why do we need the first conditional? Can't we just do if args.config_dir
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.
It's because of the (still supported) run-config
legacy option - I've only added the config-dir
subparser to the newer configs run
, so when run-config
is used, the config-dir
variable is not initialized to null and so it errors.