andrew_stewart
04/02/2021, 11:15 PMtap_mongodb or whatever.. but for some reason everything is just getting dumped into public. I’ve tried playing around with the postgres_schema config on target-postgres as well as load_schema on the individual extractors, but I keep getting errors about how the schemas don’t exist. Am I missing something or is this kind of strange?andrew_stewart
04/03/2021, 12:28 AMtarget-postgres the meltano variant supports dynamically creating schemas, while the datamill-co variant does not.taylor
04/03/2021, 1:07 AMandrew_stewart
04/03/2021, 8:38 PMandrew_stewart
04/03/2021, 9:42 PMmeltano discover loaders (for example) conveniently lists all the registered variants, ala: target-postgres, variants: datamill-co (default), transferwise, meltano
Then as far as I can tell something like meltano config target-postgres list doesn’t let you specify a particular variant.
I wonder if there’d be some utility in having a command like meltano info PLUGIN_NAME [--variant=VARIANT_NAME] which outputs some basic info on plugin, as well as any “variant notes”. For example, variants listed in discovery.yml could include some curated notes like:
- name: target-postgres
label: PostgreSQL
description: PostgreSQL database loader
namespace: target_postgres
dialect: postgres
target_schema: $TARGET_POSTGRES_SCHEMA
variants:
- name: datamill-co
notes:
- label: Automatic schema generate
value: No
- label: foo
value: bar
...
- name: meltano
original: true
notes:
- label: Automatic schema generate
value: Yes
- label: foo
value: bar
Maybe something like this already exists I’m not aware of though.andrew_stewart
04/03/2021, 9:43 PM