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

Add columns to result handler for row level metadata #686

Closed
nehanene15 opened this issue Jan 30, 2023 · 0 comments
Closed

Add columns to result handler for row level metadata #686

nehanene15 opened this issue Jan 30, 2023 · 0 comments
Assignees
Labels
priority: p0 Highest priority. Critical issue. Will be fixed prior to next release. type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.

Comments

@nehanene15
Copy link
Collaborator

Currently, DVT execution does not provide a response code with the run_id on command line execution, the user needs to go into BQ and search the execution results to find the appropriate run_id. This becomes more cumbersome when multiple executions of DVT is done at same time. DVT should log the run_id in standard output.

Add columns in the result handler for applied filters (if any), custom query applied at source/target, and columns used for hashing/concat

@nehanene15 nehanene15 changed the title Result handler optimizations Add columns to result handler for row level metadata Jan 30, 2023
@nehanene15 nehanene15 added type: feature request 'Nice-to-have' improvement, new feature or different behavior or design. priority: p0 Highest priority. Critical issue. Will be fixed prior to next release. labels Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p0 Highest priority. Critical issue. Will be fixed prior to next release. type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

3 participants