Anyone encountered this with Bigquery Denormalized...
# replication-troubleshooting
s
Anyone encountered this with Bigquery Denormalized destination? I tried syncing a table from MongoDB with quite a deep nested structure and have encountered this error:
Copy code
For more details see Big Query Error collection: BigQueryError{reason=invalid, location=null, message=Error while reading data, error message: JSON table encountered too many errors, giving up. Rows: 1; errors: 1. Please look into the errors[] collection for more details.},
 BigQueryError{reason=invalid, location=null, message=Error while reading data, error message: JSON processing encountered too many errors, giving up. Rows: 1; errors: 1; max bad: 0; error percent: 0},
 BigQueryError{reason=invalid, location=null, message=Error while reading data, error message: JSON parsing error in row starting at position 0: JSON object specified for non-record field: input.application.data.applicants}:
When I look at the schema of the tmp table that was created in Bigquery by Airbyte, it has mapped input.application.data.applicants as String + Repeated. However inspecting the data structure in JSON format it looks like it should be a repeated record, with further nested properties inside it. Is this kind of structure (items enclosed by
[{ }]
) supported currently?
m
Do you have other example of nested json objects not been parsed as a record?
s
Hi @Marcos Marx (Airbyte), I will try out a few more tables from our mongodb instance and see if i find another
Yep I am getting the same behaviour with other documents. Here is another one. When viewing in MongoDB Compass it shows the structure has two arrays of json objects which expand with more fields and further nested objects inside. (sorry for compliance reasons I can't send the actual data only the structure), but the schema generated puts them as repeated strings and I get this error in Airbyte:
BigQueryError{reason=invalid, location=null, message=Error while reading data, error message: JSON parsing error in row starting at position 0: JSON object specified for non-record field: applicants}
Another example. Anything that is displayed as an array of objects when viewing in mongodb compass will produce the same issue and error
m
@Stuart Horgan probably this is a limitation of the Mongodb connector. Do you mind opening a Github issue to improve the connector?
s
ok thanks - i will open an issue on monday
https://github.com/airbytehq/airbyte/issues/20061 issue created @Marcos Marx (Airbyte)
u
Can you upload the complete log file, it helps a lot the developer who will fix the issue.
s
sorry - couldn't figure out how to attach it yesterday, have added it now