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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Source Facebook Marketing to Bigquery Denormalized - JSON schema validation failed #9169

Closed
octavia-squidington-iii opened this issue Dec 29, 2021 · 4 comments

Comments

@octavia-squidington-iii
Copy link
Collaborator

octavia-squidington-iii commented Dec 29, 2021

Is this your first time deploying Airbyte: No
OS Version / Instance: AWS EC2 t3.Large
Memory / Disk: 8GiB / 50GB EBS
Deployment: Docker
Airbyte Version: 0.35.2-alpha
Source name/version: Facebook Marketing 0.2.30
Destination name/version: Bigquery(denormalized) 0.2.2
Step: On sync
Description: Seems to error out towards the end when it is trying to sync to bigquery. Seeing error messages such as

Validation failed: null
error message: JSON table encountered too many errors, giving up. Rows: 1; errors: 1. Please look into the errors[] collection for more details.

Slack conversation

Logs:

logs-2-2.txt

@alafanechere alafanechere added the area/connectors Connector related issues label Dec 29, 2021
@alafanechere alafanechere changed the title Facebook Marketing to Bigquery Denormalized: too many errors 馃悰 Source Facebook Marketing to Bigquery Denormalized: too many errors Dec 29, 2021
@alafanechere alafanechere changed the title 馃悰 Source Facebook Marketing to Bigquery Denormalized: too many errors 馃悰 Source Facebook Marketing to Bigquery Denormalized - JSON schema validation failed Dec 29, 2021
@alafanechere alafanechere added the type/bug Something isn't working label Dec 29, 2021
@sherifnada
Copy link
Contributor

first step is to reproduce to identify if the issue is with bigquery or facebook

@eliziario
Copy link
Contributor

I could not reproduce the error. From the logs attached here, it looks like an issue with the destination, but the information in the logs is not enough to determine the exact nature of the error.

I would need at least the destination catalog to proceed.

@VasylLazebnyk VasylLazebnyk removed this from the Connectors Jan 28 2022 milestone Jan 31, 2022
@lazebnyi lazebnyi assigned lazebnyi and unassigned eliziario and lazebnyi Mar 7, 2022
@etsybaev etsybaev self-assigned this Mar 31, 2022
@etsybaev
Copy link
Contributor

etsybaev commented Apr 9, 2022

Were there any updates from customers on this? Is this still reproducible? Can't reduce this issue

Selection_080
Selection_081
Selection_082

@etsybaev
Copy link
Contributor

Taking into consideration that nobody was able to reproduce this issue, that this ticket was raised a long time and lots of changes have been done since then (including some changes in bigquery related to facebook as per changelog) - I'm closing this ticket. I've spend pretty much time for attempts to reproduce it, but lo luck.
FYI @sherifnada

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

No branches or pull requests

9 participants