suraj
05/19/2020, 10:30 PMdouwe_maan
05/19/2020, 11:04 PMsuraj
05/19/2020, 11:09 PMsuraj
05/20/2020, 4:47 PMmeltano add --custom loader target-bigquerysuraj
05/20/2020, 4:48 PM(meltano) schokshi-2197:paperless_meltano schokshi$ meltano add --custom loader target-bigquery
The `namespace` refers to the data source name.
It is used to infer compatibility between components.
(namespace): bigquery
The `pip URL` refers to the pip installation specification.
You may provide any pip-compatible entry:
from VCS: git+<https://gitlab.com/meltano/tap-carbon-intensity.git>
from PyPI: tap-something
from Source: [-e] /path/to/plugin/source
(pip_url): <https://github.com/jmriego/pipelinewise-target-bigquery.git>
The `executable` refers to the entry point of the plugin.
By convention, plugins should use their package name as executable, but it might be useful to override it to have multiple flavors of the same plugin installed.
(executable) [target-bigquery]: target-bigquery
The `settings` refer to the configuration keys the plugin supports.
In the case of Singer taps and targets, these correspond to supported keys in `config.json`.
Nesting can be represented using the `.` seperator, e.g. `auth.username` for `{ "auth": { "username": value } }`.
Multiple setting names/keys can be specified using a comma-separated string.
(settings) [[]]: config.json
[2020-05-20 12:44:55,802|W|MainThread|root] target-bigquery is already present, use `meltano install` to install it.
The plugin has been added to your `meltano.yml`.
If your plugin requires configuration options, you can add them directly in the created plugin definition under the `settings` or `config` section.
Added 'target-bigquery' to your Meltano project.
Installing 'target-bigquery'...
target-bigquery has an installation issue. Failed to install plugin 'target-bigquery'.
ERROR: Cannot unpack file /private/var/folders/1l/dmj4h7xj6jb663wnmpjbrr6w6dpk4k/T/pip-unpack-r1stkkyk/pipelinewise-target-bigquery.git (downloaded from /private/var/folders/1l/dmj4h7xj6jb663wnmpjbrr6w6dpk4k/T/pip-req-build-sd7ps0w3, content-type: text/html; charset=utf-8); cannot detect archive format
ERROR: Cannot determine archive format of /private/var/folders/1l/dmj4h7xj6jb663wnmpjbrr6w6dpk4k/T/pip-req-build-sd7ps0w3
WARNING: You are using pip version 19.2.3, however version 20.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Aborted!douwe_maan
05/20/2020, 4:57 PMgit+ prefix on your pip_url ! pip3 install won't handle the URL correctly unless it knows what VCS tool to use to clone the provided URL 🙂suraj
05/20/2020, 5:16 PMsuraj
05/20/2020, 5:18 PM# Specify supported settings (`config.json` keys)
(settings):
when i run meltano elt tap-zendesk target-bigquery i get the error:
(meltano) schokshi-2197:paperless_meltano schokshi$ meltano elt tap-zendesk target-bigquery
[2020-05-20 13:10:26,205|I|MainThread|alembic.runtime.migration] Context impl SQLiteImpl.
[2020-05-20 13:10:26,205|I|MainThread|alembic.runtime.migration] Will assume non-transactional DDL.
System database up-to-date.
Running extract & load...
No state was found, complete import.
INFO Using API Token authentication.
ERROR Invalid configuration:
* Required key is missing from config: [project_id]
* Neither 'default_target_schema' (string) nor 'schema_mapping' (object) keys set in config.
INFO tickets: Starting sync
INFO METRIC: {"type": "timer", "metric": "http_request_duration", "value": 5.647816896438599, "tags": {"status": "succeeded"}}
INFO Syncing ticket_audits per ticket...
INFO Starting metrics capture at 2020-05-20T17:10:35Zdouwe_maan
05/20/2020, 5:20 PM(settings): prompt? Based on https://github.com/jmriego/pipelinewise-target-bigquery#configuration-settingsd, the minimal settings would be dataset_id,project_iddouwe_maan
05/20/2020, 5:21 PMtemp_schema,default_target_schema , etc, you'll want to make sure you edit meltano.yml to set their default values for these settings by adding value properties to the appropriate objects under settingsdouwe_maan
05/20/2020, 5:22 PMsuraj
05/20/2020, 6:00 PMsuraj
05/20/2020, 6:01 PM