Skip to content
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 result handler to support different validation types #298

Closed
nehanene15 opened this issue Aug 19, 2021 · 1 comment
Closed

Refactor result handler to support different validation types #298

nehanene15 opened this issue Aug 19, 2021 · 1 comment
Assignees
Labels
priority: p1 High priority. Fix may be included in the next release. Release Next release candidate type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.

Comments

@nehanene15
Copy link
Collaborator

nehanene15 commented Aug 19, 2021

Now that DVT supports row level validation, the result handler needs to add the following fields:

  • primary_keys
  • num_random_rows
  • filter fields (nice to have)
@nehanene15 nehanene15 added priority: p1 High priority. Fix may be included in the next release. Release Next release candidate labels Aug 19, 2021
@nehanene15 nehanene15 self-assigned this Aug 19, 2021
@nehanene15 nehanene15 added the type: feature request 'Nice-to-have' improvement, new feature or different behavior or design. label Aug 19, 2021
@nehanene15
Copy link
Collaborator Author

Take into consideration Issue #310 for result handler redesign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p1 High priority. Fix may be included in the next release. Release Next release candidate type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants