Wrong Schema in Postgres Target

[lmorroni]

Hello,
I am using Meltano and I am using a tap that is wrapped in the tap-airbyte-wrapper. tap-jira to be specific. When I try loading it to target-postgres, the schema is set to tap-airbyte. I'd like to be able to override this to the name of the tap(tap-jira). I looked in the configs and saw nothing to support this except default_target_schema in target-postgres. That doesn't help me though because I am using multiple tap-airbyte-wrapper taps.

Is this a config setting that needs to be created or a bug?

Thank You,

Larry

[nickjoanis]

Hi @lmorroni,

If I understand your use case correctly, you’d like each tap using tap-airbyte-wrapper to write to a different target schema. Since default_target_schema is defined statically in meltano.yml, Meltano won’t allow separate schema values per tap through the YAML alone.

However, Meltano does support overriding configuration via environment variables: https://docs.meltano.com/guide/configuration/

In our case, we deploy each sync independently, which allows us to control the environment at execution time rather than relying on the hard-coded value in meltano.yml. We simply set TARGET_POSTGRES_DEFAULT_TARGET_SCHEMA to the appropriate schema before running the sync, ensuring each tap writes to the correct destination schema. I haven’t tested this recently with the Postgres target specifically, but we use this same approach successfully with other targets we’ve developed internally.

Hope this helps!