validate column: PostgreSQL False negative validation of timestamps with epoch seconds at high volume #1391
Labels
priority: p1
High priority. Fix may be included in the next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
When validating timestamps using
--wildcard-include-timestamp
we can get a failed validation for columns that should match.Test tables
Oracle
PostgreSQL
BigQuery
Test commands
Oracle vs BigQuery (success):
Oracle vs PostgreSQL (fail):
Research
The PostgreSQL query was the one below which has the correct result:
I debugged the validation and at the point we fetch data from PostgreSQL we get the correct result:
But in the same code we enter this section of code, note that Pandas sees
Decimal
as an object):And after the
coerce_float
section completes the data has been converted from an integer to a floating point value and become lossy:The text was updated successfully, but these errors were encountered: