Normalisation fails on Hubspot to PostgreSQL

Connector Questions & Issues
, ,
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Amazon Linux 2 AMI
  • Memory / Disk: 100Gb
  • Deployment: Docker
  • Airbyte Version: 0.38-2alpha
  • Source name/version: Hubspot - 0.1.59
  • Destination name/version: PostgreSQL- 0.3.19
  • Step: The issue is happening during sync
  • Description: Getting the following error during normalization
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2022-03-03 21:09:09
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2020-06-23 15:29:42
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2020-06-23 15:29:42
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2020-06-23 15:29:42
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2020-06-23 15:29:49
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2020-06-23 15:29:42
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2020-06-23 15:29:42
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2020-06-23 15:29:43
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2022-03-03 21:09:09
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2021-01-19 19:31:32
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2020-07-07 21:21:23
2022-05-16 04:21:34 ERROR c.n.s.DateTimeValidator(isLegalDateTime):70 - Failed to apply RFC3339 pattern on 2022-05-15 16:01:31
2022-05-16 04:21:34 WARN i.a.w.DefaultReplicationWorker(lambda$getReplicationRunnable$5):298 - Record schema validation failed. Errors: json schema validation failed when comparing the data to the json schema. 
Errors: $.properties.hs_email_first_open_date: 2020-07-07 21:21:28 is an invalid date-time, $.properties.hs_analytics_first_timestamp: 2020-06-23 15:29:42 is an invalid date-time, $.properties.hubspot_owner_assigneddate: 2021-04-12 20:02:36 is an invalid date-time, $.properties.hs_email_last_open_date: 2021-01-19 19:41:26 is an invalid date-time, $.properties.hs_date_entered_lead: 2022-03-03 21:09:09 is an invalid date-time, $.properties.first_conversion_date: 2020-06-23 15:29:42 is an invalid date-time, $.properties.hs_analytics_last_timestamp: 2020-06-23 15:29:42 is an invalid date-time, $.properties.hs_analytics_last_visit_timestamp: 2020-06-23 15:29:42 is an invalid date-time, $.properties.closedate: 2020-06-23 15:29:49 is an invalid date-time, $.properties.hs_analytics_first_visit_timestamp: 2020-06-23 15:29:42 is an invalid date-time, $.properties.recent_conversion_date: 2020-06-23 15:29:42 is an invalid date-time, $.properties.createdate: 2020-06-23 15:29:43 is an invalid date-time, $.properties.hs_lifecyclestage_lead_date: 2022-03-03 21:09:09 is an invalid date-time, $.properties.hs_email_last_send_date: 2021-01-19 19:31:32 is an invalid date-time, $.properties.hs_email_first_send_date: 2020-07-07 21:21:23 is an invalid date-time, $.properties.lastmodifieddate: 2022-05-15 16:01:31 is an invalid date-time
2

Hey looks the value which is returned doesn’t map with thedestination. To validate can you try with different destination?

3

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.