proud-pillow-55935
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.salmon-salesclerk-77709
03/25/2021, 2:43 PMproud-pillow-55935
03/25/2021, 2:44 PMsalmon-salesclerk-77709
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?proud-pillow-55935
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:
meltano.yml
before I use that?salmon-salesclerk-77709
03/25/2021, 3:31 PMsalmon-actor-23953
03/25/2021, 3:39 PMripe-musician-59933
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>"}'
meltano.yml
instead of injecting it at runtime using the environment