GoogleCloudPlatform / GoogleCloudPlatform/professional-services-data-validator
Teradata : Print Teradata query ID in DVT logs
- Dominant language
- Python
- Stars
- 524
- Forks
- 171
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 4
Description
**Is your feature request related to a problem? Please describe.**
This is an urgent request from a customer who is leveraging DVT for row level validation during their TD2BQ migration. They are incurring high costs for their TD queries, and would like to do further analysis into which tables are contributing the most to the costs.
**What version of DVT are you using?**
7.6 (latest)
**What type of connections are you using for source and target?**
Teradata for Source
BigQuery for Target
**Describe the solution you'd like**
DVT prints the TD query ID during execution. This can be specific to log-level=DEBUG so as to not show up in every execution.
**How are you executing DVT?**
Cloud Run job invoking DVT via shell script
Contributor guide
Assessment
This issue has not been assessed yet.