Reading about the default variant for

target-postgres

over at https://hub.meltano.com/loaders/postgres, it describes the default value of

postgres_schema

like so:

Default:

$MELTANO_EXTRACT__LOAD_SCHEMA

, which will expand to the value of the `load_schema` extra for the extractor used in the pipeline, which defaults to the extractor’s namespace, e.g.

tap_gitlab

for

tap-gitlab

.

Does anyone know what is setting that

MELTANO_EXTRACT__LOAD_SCHEMA

with the extractor’s namespace? It doesn’t look like it’s part of the actual

target-postgres

code? So maybe it’s part of the plugin?

@andrew_stewart Meltano populates that env var based on the value of the load_schema extra on the tap. As you can see if you follow that link, that extra defaults to the tap’s namespace

Right, I followed that part. I’m curious what is populating the

load_schema

extra. Like what is setting that default?

Aha

The default value for

postgres_schema

is, yeah. If you have a custom plugin definition for

target-athena

in

meltano.yml

, you could similarly set it there under

settings

Should also work for custom plugins directly in

meltano.yml

?

Yep!

Cool, wasn’t sure if the order of evaluation would suppor that.

Nope, should be good 🙂

I’m excited!

We agree, thanks for working on it!