GoogleCloudPlatform / GoogleCloudPlatform/professional-services-data-validator

Row Validation with BQ fails when a primary key column is a timestamp for Oracle, Postgres, Sqlserver and Teradata (MySQL succeeds)

Open
#1,613 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
524
Forks
171
Avg merge
5d 15h
Merged PRs (30d)
4

Description

As part of the work on [issue ](https://github.com/GoogleCloudPlatform/professional-services-data-validator/issues/1538) we added an end-to-end validation test for `generate-table-partitions`. Prior tests only generated partition config and didn't run the configs.

The new tests fail on Oracle and PostgreSQL.

Oracle:
```
E TypeError: Arguments approved:boolean and Literal(N):string are not comparable
```

PostgreSQL:
```
E data_validation.exceptions.ValidationException: Some of the validations raised an exception

data_validation/__main__.py:417: ValidationException
------------------------------------------------------------------------- Captured log call --------------------------------------------------------------------------
ERROR root:__main__.py:411 Error 'You are trying to merge on datetime64[ns] and datetime64[ns, UTC] columns. If you wish to proceed you should use pd.concat' occurred while running config file 0001.yaml. Skipping it for now.
ERROR root:__main__.py:411 Error 'You are trying to merge on datetime64[ns] and datetime64[ns, UTC] columns. If you wish to proceed you should use pd.concat' occurred while running config file 0000.yaml. Skipping it for now.
```

Search for issue-1613 in integration tests after the Sybase implementation has been merged.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.