Caio César P. Ricciuti
12/01/2022, 7:38 AMRahul Borse
12/01/2022, 7:54 AMQamarudeen Muhammad
12/01/2022, 9:59 AMlaila ribke
12/01/2022, 10:08 AMlaila ribke
12/01/2022, 10:17 AMMads Christensen
12/01/2022, 10:22 AMTmac Han
12/01/2022, 10:23 AMTmac Han
12/01/2022, 10:30 AMStuart Horgan
12/01/2022, 11:49 AMFor 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?miles trevethan
12/01/2022, 12:36 PMPrashant Jha
12/01/2022, 1:42 PMRoyzac
12/01/2022, 3:40 PMFariha Baloch
12/01/2022, 4:18 PM데이브
12/01/2022, 4:56 PMKalaSai
12/01/2022, 5:20 PMGraeme Morrell
12/01/2022, 5:50 PMCarolina Buckler
12/01/2022, 6:08 PMError: common.error
Discovering schema failed
Max retries exceeded with url
Stream Account cannot be processed by REST or BULK API.
Brian Nelson
12/01/2022, 6:25 PMRajkishore Balabadruni
12/01/2022, 9:35 PMMazin Zreik
12/01/2022, 10:11 PMThe connection tests failed.
non-json response
• Airbyte version (open source): 0.40.23
• Deployed on EC2
• Connector Version: 0.3.51
Any ideas what can be the reason?Denis Samuylov
12/01/2022, 11:35 PMError: failed pre-install: timed out waiting for the condition
. If I list all resources created in the namespace, I can see that the pod pod/airbyte-airbyte-bootloader
is running, and 2 other pods (pod/airbyte-db-0
and pod/airbyte-minio-0
) are pending which seems to be an issue with `PersistentVolumeClaims`:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal NotTriggerScaleUp 3m32s (x21 over 23m) cluster-autoscaler pod didn't trigger scale-up: 2 pod has unbound immediate PersistentVolumeClaims
Warning FailedScheduling 37s (x25 over 24m) default-scheduler 0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
Anybody had a similar problem? Any ideas how to fix it?Pameli Roy
12/02/2022, 6:21 AMPameli Roy
12/02/2022, 6:22 AM{"type": "LOG", "log": {"level": "FATAL", "message": "Modelname.path() got an unexpected keyword argument 'stream_state'\nTraceback (most recent call last):\n
Pameli Roy
12/02/2022, 6:22 AMPameli Roy
12/02/2022, 6:22 AMlucien
12/02/2022, 8:12 AM郭子麒 (數據管理部)Jacky Kwok
12/02/2022, 9:51 AMPhani Sura
12/02/2022, 9:58 AMMariam Thiam
12/02/2022, 10:17 AMPaweł M
12/02/2022, 10:31 AM