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

Source Pipedrive - normalization fails when syncing data because of the format of date fields #21377

Closed
marcNY opened this issue Jan 13, 2023 · 2 comments

Comments

@marcNY
Copy link

marcNY commented Jan 13, 2023

Environment

  • Airbyte version: 0.40.17
  • OS Version / Instance: GCP n2
  • Deployment: Docker
  • Source Connector and version: Pipedrive ALPHA 0.1.13
  • Destination Connector and version: BigQuery 1.2.9
  • Step where error happened: Sync job

Current Behavior

The Sync Job is failing during the normalization stage

Expected Behavior

The Sync Should finish successfully

Logs

5ea0e06e_6fbf_4423_ad86_b288e6f329a4_logs_17_txt.txt

Steps to Reproduce

  1. Create the connector with "Normalized tabular data" transformation
  2. Start the Sync
  3. The sync will fail

Are you willing to submit a PR?

Sure If I am able to find the error

@marcNY marcNY added needs-triage type/bug Something isn't working labels Jan 13, 2023
@marcNY marcNY changed the title Pipedrive normalisation fails Pipedrive normalization fails when syncing data because of the format of date fields Jan 13, 2023
@sajarin sajarin changed the title Pipedrive normalization fails when syncing data because of the format of date fields Source Pipedrive - normalization fails when syncing data because of the format of date fields Jan 23, 2023
@grubberr
Copy link
Contributor

grubberr commented Mar 1, 2023

similar problem #18785

I suspect the problem can be here
https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/connectors/source-pipedrive/source_pipedrive/schemas/deals.json#L166

Airbyte testing data have "null" for all records for this field and I cannot reproduce this problem for now.

Keeping an eye on this problem ...

@grubberr
Copy link
Contributor

Fixed in this PR #23789

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants