Having problem setting up BigQuery Destinaton via Airbyte UI

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: macOS
  • Memory / Disk: 512GB
  • Deployment: Docker
  • Airbyte Version: Latest
  • Source name/version:
  • Destination name/version:
  • Step: The issue is happening during creating a new BigQuery destination
  • Description: I’m basically following this tutorial Data Stack for Machine Learning - Made With ML. Yesterday, everything worked fine, but I had some problems with dbt because of setting Dataset Location to EU instead of US while I was creating BigQuery Destination via Airbyte UI.
    I decided to start everything over today and make a Dataset Location set to US. I’m using GCP Free Tier ($300 free credits), created Service Account, generated Key and copied everything form JSON file into the field “Service Account Key JSON (Required for cloud, optional for open-source)”, but today I’ve got an error:

The connection tests failed.

Failed to check connection: Access Denied: BigQuery BigQuery: Streaming insert is not allowed in the free tier

Yesterday I could create a Destination (BigQuery), and Connection via Airbyte UI, ingest the data into the BigQuery but today all of a sudden I have the error from above.

Problem solved by attaching a billing account to my GCP project. Also, that billing account uses free tier of $300.

Here is tutorial for you random Internet stranger:

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

1 Like

Thanks for the update and glad you got this resolved!