Datetime field saved as dictionary in S3 parquet

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Amazon Linux - EC2 t2.large
  • Memory / Disk: 8Gb / 30Gb
  • Deployment: Docker
  • Airbyte Version: 0.40.6
  • Source name/version: MySQL - 0.6.11
  • Destination name/version: S3 - 0.3.15
  • Step: Issue happens during sync
  • Description:

While synching a MySQL database to S3 Parquet, timestamp fields are beying converted to a dictionary structure:
{"member0": "2020-02-04T17:01:27.000+0000", "member1": null}

Upon upgrading to AirByte 0.40.7, I get this log error:

2022-09-20 05:33:02 ERROR c.n.s.DateTimeValidator(tryParse):82 - Invalid date-time: No timezone information: 2022-06-24T16:34:37.000000
2022-09-20 05:33:02 ERROR c.n.s.DateTimeValidator(tryParse):82 - Invalid date-time: No timezone information: 2022-06-24T16:34:36.000000
2022-09-20 05:33:02 ERROR c.n.s.DateTimeValidator(tryParse):82 - Invalid date-time: No timezone information: 2022-06-24T16:34:37.000000
2022-09-20 05:33:02 ERROR c.n.s.DateTimeValidator(tryParse):82 - Invalid date-time: No timezone information: 2021-08-20T13:54:58.000000

The data is simply being loaded from a datetime field of a MySQL database. I noticed that using older versions of the MySQL source connector, like 0.6.1, works properly.

Any help fixing this is appreciated!

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

Is downgrading Airbyte the only solution for this problem?

After testing multiple MySQL source connector versions, I downgraded to version 0.6.2, and now the behavior described above is not happening anymore. Now, datetime fields are being saved as strings again, and not as objects.

Hey team is looking into it. Date type written as dictionary for parquet format in s3 destination · Issue #14028 · airbytehq/airbyte · GitHub we are also facing the same in the cloud. In the meantime you can use the lower version and use custom dbt to convert the string into datetime if that makes sense

1 Like