-
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
refactor: custom query code #607
Conversation
/gcbrun |
/gcbrun |
Can you also update the README with the following:
|
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.
Have we tested with saving the custom query validation to YAML and then running it?
Does this support comparison field validations or only hash/concat?
Yes. We tested generating the yaml config and then running the validation using config file. Works as expected. |
Done here |
/gcbrun |
/gcbrun |
/gcbrun |
/gcbrun |
/gcbrun |
/gcbrun |
/gcbrun |
/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.
Logic looks good, just suggested some code style changes.
/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.
Approved. Suggested one last comment to delete the query_type in the arg parser since it is not used.
/gcbrun |
This PR includes following changes:
Instead of constructing nested queries manually using string concatenation, we now use ibis framework similar to how we construct queries for regular validations.
source-query-file
andtarget-query-file
mandatory for custom-query validation commands.primary-keys
flag mandatory for custom-query row validation.