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

Fix BigQuery destination normalization to accept any date-time format. #7776

Closed
alafanechere opened this issue Nov 9, 2021 · 0 comments · Fixed by #8483
Closed

Fix BigQuery destination normalization to accept any date-time format. #7776

alafanechere opened this issue Nov 9, 2021 · 0 comments · Fixed by #8483

Comments

@alafanechere
Copy link
Contributor

alafanechere commented Nov 9, 2021

A user using a Marketo to BigQuery connection is facing a bug during basic normalization (slack message here).
It appears that the Marketo connector is outputting a date-time format which is not properly handled by BigQuery leading to the following normalization error:
Invalid timestamp: '2018-09-07T17:37:18Z+0000'.

This issue is closely related to a similar normalization problem with Snowflake (#5713)

Environment

  • Airbyte version: 0.30.33-alpha
  • OS Version / Instance: n1-standard-2
  • Deployment: Docker
  • Source Connector and version: airbyte/source-marketo:0.1.0
  • Destination Connector and version: airbyte/destination-bigquery:0.5.0
  • Severity: High
  • Step where error happened: Sync job

Current Behavior

Marketo source outputs date-time format such as 2018-09-07T17:37:18Z+0000 in the createdAt field of the Program's stream records.
Normalization fails with Invalid timestamp: '2018-09-07T17:37:18Z+0000' error.

Expected Behavior

BigQuery normalization should handle casting this format to timestamp.

Logs

logs-18-2-marketo.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants