Does anyone know why the meltano invoke tap-mssql ...
# troubleshooting
h
Does anyone know why the meltano invoke tap-mssql --discover command doesn't use the config from the meltano.yml file? And when I run the same command with the -c config.json option with the same data from the meltano.yml file, the command performs the discovery without problems, I need help. Please anyone knows about that?
r
What does
meltano config tap-mssql list
show?
h
list valus from meltano.yml file (from
meltano.yml
)
It's very rare
e
Hi @hugo_vargas. How does your
meltano.yml
look like? (with any secrets obfuscated)
h
version: 1 default_environment: dev environments: - name: dev - name: staging - name: prod project_id: meltano-test-e5a3b6ee-6d57-4c54-811b-d8f0f60e47ba plugins: extractors: - name: tap-mssql variant: wintersrd pip_url: tap-mssql config: database: ms filter_dbs: ms host: ip port: '1433' user: xxx default_replication_method: FULL_TABLE - name: tap-postgres variant: transferwise pip_url: pipelinewise-tap-postgres config: dbname: postgres default_replication_method: FULL_TABLE filter_schemas: public host: ip user: user loaders: - name: target-postgres variant: transferwise pip_url: pipelinewise-target-postgres config: dbname: target default_target_schema: public host: ip user: user orchestrators: - name: airflow variant: apache pip_url: apache-airflow==2.3.4 --constraint https://raw.githubusercontent.com/apache/airflow/constraints-2.3.4/constraints-${MELTANO__PYTHON_> transformers: - name: dbt-postgres variant: dbt-labs pip_url: dbt-core~=1.1.0 dbt-postgres~=1.1.0 schedules: - name: mssql-to-postgres interval: '@once' extractor: tap-mssql loader: target-postgres transform: skip start_date: 2022-08-26 205322.142596
e
Does
meltano invoke tap-mssql
use the right config?
h
I don't know, when i run meltano invoke tap-postgres the command use tap-postgres configs from meltano.yml file. But when i run with tap-mssql it's like that the command not use configs from meltano.yml file and return: { streams: [] } But if i use -c with config.json file option, the command returns schema datas correctly, it's like the tap-mssql not choose use configs from meltano.yml file and ignore it
I give up, it doesn't work, it's useful for postgres but it's useless for sql server, I'll write a full python airflow DAG to extract the data from SQL server, for now Meltano is useless for me