Skip to main content

Google BigQuery target of singer.io framework.

Project description

target-bigquery

ANELEN's implementation of target-bigquery.

This is a Singer target that loads JSON-formatted data following the Singer spec to Google BigQuery.

Installation

Step 0: Acknowledge LICENSE and TERMS

Please especially note that the author(s) of target-bigquery is not responsible for the cost, including but not limited to BigQuery cost) incurred by running this program.

Step 1: Activate the Google BigQuery API

(originally found in the Google API docs)

  1. Use this wizard to create or select a project in the Google Developers Console and activate the BigQuery API. Click Continue, then Go to credentials.
  2. On the Add credentials to your project page, click the Cancel button.
  3. At the top of the page, select the OAuth consent screen tab. Select an Email address, enter a Product name if not already set, and click the Save button.
  4. Select the Credentials tab, click the Create credentials button and select OAuth client ID.
  5. Select the application type Other, enter the name "Singer BigQuery Tap", and click the Create button.
  6. Click OK to dismiss the resulting dialog.
  7. Click the Download button to the right of the client ID.
  8. Move this file to your working directory and rename it client_secrets.json.

Export the location of the secret file:

export GOOGLE_APPLICATION_CREDENTIALS="./client_secret.json"

For other authentication method, please see Authentication section.

Step 2: Install

First, make sure Python 3 is installed on your system or follow these installation instructions for Mac or Ubuntu.

pip install -U target-bigquery-partition

Or you can install the lastest development version from GitHub:

pip install --no-cache-dir https://github.com/anelendata/target-bigquery/archive/master.tar.gz#egg=target-bigquery

Run

Step 1: Configure

Create a file called target_config.json in your working directory, following config.sample.json:

{
    "project_id": "your-gcp-project-id",
    "dataset_id": "your-bigquery-dataset",
    "table_prefix": "optional_table_prefix",
    "table_ext": "optional_table_ext",
    "partition_by": "optional_column_name",
    "partition_type": "day",
    "partition_exp_ms": null,
    "stream": false,
}

Notes:

  • The table name is set as stream name from the tap. You can add prefix and ext to the name.
  • Optionally, you can set partition_by to create a partitioned table. Many production quailty taps implements a ingestion timestamp and it is recommended to use the column here to partition the table. It will increase the query performance and lower the BigQuery costs. partition_type can be hour, day, month, or year and the default is day. partition_exp_ms sets the partition expiration in millisecond. Default is null (never expire).
  • stream: Make this true to run the streaming updates to BigQuery. Note that performance of batch update is better when keeping this option false.

Step 2: Run

target-bigquery can be run with any Singer Target. As example, let use tap-exchangeratesapi.

pip install tap-exchangeratesapi

Run:

tap-exchangeratesapi | target-bigquery -c target_config.json

Authentication

It is recommended to use target-bigquery with a service account.

  • Download the client_secrets.json file for your service account, and place it on the machine where target-bigquery will be executed.
  • Set a GOOGLE_APPLICATION_CREDENTIALS environment variable on the machine, where the value is the fully qualified path to client_secrets.json

In the testing environment, you can also manually authenticate before runnig the tap. In this case you do not need GOOGLE_APPLICATION_CREDENTIALS defined:

gcloud auth application-default login

You may also have to set the project:

gcloud config set project <project-id>

Though not tested, it should also be possible to use the OAuth flow to authenticate to GCP as well:

  • target-bigquery will attempt to open a new window or tab in your default browser. If this fails, copy the URL from the console and manually open it in your browser.
  • If you are not already logged into your Google account, you will be prompted to log in.
  • If you are logged into multiple Google accounts, you will be asked to select one account to use for the authorization.
  • Click the Accept button to allow target-bigquery to access your Google BigQuery table.
  • You can close the tab after the signup flow is complete.

Original repo

https://github.com/anelendata/target-bigquery

About this project

This project is developed by ANELEN and friends. Please check out the ANELEN's open innovation philosophy and other projects

ANELEN

Copyright © 2020~ Anelen Co., LLC

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

target-bigquery-partition-0.2.0.tar.gz (12.6 kB view details)

Uploaded Source

Built Distribution

target_bigquery_partition-0.2.0-py3-none-any.whl (14.0 kB view details)

Uploaded Python 3

File details

Details for the file target-bigquery-partition-0.2.0.tar.gz.

File metadata

  • Download URL: target-bigquery-partition-0.2.0.tar.gz
  • Upload date:
  • Size: 12.6 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.2.0 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.7.5

File hashes

Hashes for target-bigquery-partition-0.2.0.tar.gz
Algorithm Hash digest
SHA256 1ff47eea0d2271ec8fed2e020345f1f394e6e6a7b054ca7885f495daf6a613aa
MD5 3b29eb38b98affb4ad56ca56ff6fa7f3
BLAKE2b-256 80a2a4843d9c4f7ff3d7ffc2532879a6b8ac6778ec22eeb78291a2f64a404178

See more details on using hashes here.

File details

Details for the file target_bigquery_partition-0.2.0-py3-none-any.whl.

File metadata

  • Download URL: target_bigquery_partition-0.2.0-py3-none-any.whl
  • Upload date:
  • Size: 14.0 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.2.0 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.7.5

File hashes

Hashes for target_bigquery_partition-0.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 ea4c23350087f3ed2ba2672cf2385ab09cb42213bad9879c70ae84c83b38e001
MD5 2db3b66549f94b712d0b29f509775aa8
BLAKE2b-256 3aa8b40645ebc62f5313bd7851ba6f88162ad83e3380b4461e0db03f5774187a

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page