The target-gcs Meltano loader pulls data from Google Cloud Storage that can then be sent to a destination using a loader.
Other Available Variants
- datateer (default)
Getting Started
Prerequisites
If you haven't already, follow the initial steps of the Getting Started guide:
Installation and configuration
-
Add the target-gcs loader to your project
using
:meltano add
-
Configure the target-gcs settings using
:meltano config
meltano add loader target-gcs
meltano config target-gcs set --interactive
Next steps
Follow the remaining steps of the Getting Started guide:
If you run into any issues, learn how to get help.
Capabilities
The current capabilities fortarget-gcs
may have been automatically set when originally added to the Hub. Please review the
capabilities when using this loader. If you find they are out of date, please
consider updating them by making a pull request to the YAML file that defines the
capabilities for this loader.This plugin has the following capabilities:
You can
override these capabilities or specify additional ones
in your meltano.yml
by adding the capabilities
key.
Settings
The
target-gcs
settings that are known to Meltano are documented below. To quickly
find the setting you're looking for, click on any setting name from the list:
You can
override these settings or specify additional ones
in your meltano.yml
by adding the settings
key.
Please consider adding any settings you have defined locally to this definition on MeltanoHub by making a pull request to the YAML file that defines the settings for this plugin.
(bucket_name)
-
Environment variable:
TARGET_GCS_BUCKET_NAME
The name of the GCS Bucket to sync the stream to
(credentials_file)
-
Environment variable:
TARGET_GCS_CREDENTIALS_FILE
-
Default Value:
$MELTANO_PROJECT_ROOT/client_secrets.json
The fully resolved path to the credentials json file. By default we will look in the meltano project directory root for a file called client_secrets.json
(date_format)
-
Environment variable:
TARGET_GCS_DATE_FORMAT
-
Default Value:
%Y-%m-%d
The date formate for the export date used in the bucket key path
(key_prefix)
-
Environment variable:
TARGET_GCS_KEY_PREFIX
-
Default Value:
meltano/${MELTANO_EXTRACT__LOAD_SCHEMA}/
This is the base key prefix which lets you define where the stream will write to in the bucket. By default, we use meltano/${MELTANO_EXTRACT__LOAD_SCHEMA}/
which is derived from the tap. For example tap-jira would end up in meltano/tap_jira/...
(key_naming_convention)
-
Environment variable:
TARGET_GCS_KEY_NAMING_CONVENTION
-
Default Value:
{stream}/export_date={date}/{timestamp}.jsonl
This is the naming convention for the key. Available values in the format string are stream (stream name), date, timestamp. By default this naming convention uses hive style partitioning
Something missing?
This page is generated from a YAML file that you can contribute changes to.
Edit it on GitHub!Looking for help?
#plugins-general
channel.
Install
meltano add loader target-gcs
Homepage
Maintenance Status
Meltano Stats
Keywords