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

Configuration for comparing dates with correct format - row hash audit #534

Closed
PraveenAkunuru opened this issue Jul 8, 2022 · 2 comments
Labels
priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@PraveenAkunuru
Copy link

For the row hash audits, We are trying to do some audit between TD and BigQuery. The row hash audit failed, due to a difference in the default cast of dates in TD and BQ. One Example -:

In TD - 1989/08/06

In BQ – 1989-08-06

Is there a way to fix/ cast these at the tool level, rather than at the source/ target level?

@PraveenAkunuru PraveenAkunuru changed the title Configuration for comparing dates Configuration for comparing dates with correct format - row hash audit Jul 8, 2022
@latika-wadhwa latika-wadhwa removed their assignment Nov 4, 2022
@nehanene15 nehanene15 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) labels Nov 22, 2022
@nehanene15
Copy link
Collaborator

nehanene15 commented Nov 22, 2022

This would likely involve adding support for the FORMAT function in Teradata/BQ

SELECT
   CAST( (CAST (F1 AS FORMAT 'YYYY-MM-DD')) AS CHAR(10))
   FROM INTDAT;

Teradata docs link

@piyushsarraf piyushsarraf self-assigned this Dec 28, 2022
@piyushsarraf piyushsarraf removed their assignment Feb 10, 2023
@nehanene15
Copy link
Collaborator

Closed with #747

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

4 participants