ricky_renner
03/25/2021, 2:42 PM<EXTRACTOR>__SCHEMA variable to include multiple different streams with different column definitions? I'm looking specifically at this documentation.taylor
03/25/2021, 2:43 PMricky_renner
03/25/2021, 2:44 PMtaylor
03/25/2021, 2:46 PMexport <EXTRACTOR>__SCHEMA_<ENTITY>_<ATTRIBUTE>_<KEY>=<value>
seems to be the answer but, full disclosure, I’ve never done this. do you have the different stream definitions?ricky_renner
03/25/2021, 3:05 PM# Once schema descriptions have been set in `meltano.yml`, environment variables can be used
# to override specific nested properties:ricky_renner
03/25/2021, 3:05 PMmeltano.yml before I use that?taylor
03/25/2021, 3:31 PMtaylor
03/25/2021, 3:31 PMaaronsteers
03/25/2021, 3:39 PMaaronsteers
03/25/2021, 3:42 PMdouwe_maan
03/25/2021, 6:17 PMTAP_FOO__SCHEMA , which you'll want to set it to a JSON-encoded dictionary with a top-level key for each stream.
If you want to use a separate env var for each stream, you'll first have to add a key for each stream to meltano.yml , which can look like this:
schema:
stream_one: {}
stream_two: {}
You can then use TAP_FOO__SCHEMA_STREAM_ONE='{"<attribute>": {"<key>": "<value>"}'douwe_maan
03/25/2021, 6:18 PMmeltano.yml instead of injecting it at runtime using the environmentdouwe_maan
03/25/2021, 6:19 PM