https://linen.dev logo
Join Slack
Powered by
Is there a way to disable this heck or resolve thi...
# troubleshooting
k
Is there a way to disable this heck or resolve this issue with 'multiple environment variables' error message? In one of the extractors, I'm setting this variable via interactive. It seems like extractor is the one that's using two environment variable names. Then, when I try to run 
elt
command, it gives this error: 
Error: Setting value set via multiple environment variables: ['TAP_HUBSPOT_AIRBYTE_CONFIG_CREDENTIALS_ACCESS_TOKEN', 'TAP_AIRBYTE_AIRBYTE_CONFIG_CREDENTIALS_ACCESS_TOKEN']
. Is there a way to bypass this error message or override the extractor to only use one env var?
e
Can you comment out one of the values in 
.env
?
k
there's only one set in .env
it only has 'TAP_HUBSPOT_AIRBYTE_CONFIG_CREDENTIALS_ACCESS_TOKEN' set in .env, the other one is nowhere to be found. This is very confusing.
This is from using 
<https://hub.meltano.com/extractors/tap-hubspot--airbyte/>
extractor.
For now, I ended up commenting out
Copy code
#if len(vals_with_metadata) > 1:
            #if reduce(eq, (val for val, _ in vals_with_metadata)):
            #    raise MultipleEnvVarsSetException(
            #        [metadata["env_var"] for _, metadata in vals_with_metadata],
            #    )
            #raise ConflictingSettingValueException(
            #    [metadata["env_var"] for _, metadata in vals_with_metadata],
            #)
in file 
.local/share/pipx/venvs/meltano/lib/python3.9/site-packages/meltano/core/settings_store.py
and made 
el
command work, but definitely a hack for now.
👀 1
Not really sure why it cares if two envs have the same value. (though I'm not setting them, maybe something's wrong with the extractor, but regardless, it probably shouldn't matter?)
e
What does your 
meltano.yml
look like?
k
neither of those two variables are in 
meltano.yml
as it's one of those redacted field. So, only one of them in 
.env
. I've tried deleting it from 
.env
, then just setting one env var using 
export
, but the same error message.
I've done unset on both env var names too to make sure.
I've also tried clean environment, but same error message. Oddly, it's only when trying to run scheduler/airflow, not if I just run it directly using 
run
.
r
Running into this too - I have one entry per setting only in my 
.env
and I get the same error. Seems to happen when the plugin 
name
and 
namespace
differ significantly, as in this case, and only when running 
el/elt
(not 
run
)...
k
Yes, seems like there are issues. But @Reuben (Matatika) you will probably run into other issues, such as states not being saved properly etc. So incremental doesn't work. So, I just ended up installing airbyte itself to evaluate. It's working better, but so far, incremental isn't fast enough yet. Will see how it goes.
r
18 Views
Open in Slack
PreviousNext
Powered by