Hey folks 👋 I hope everyone is doing well. I am fairly new with Meltano and I am trying to run a POC with

tap-mysql

(bin log replication) and

target-redshift

and meltano=1.84.0. I have a MySQL db (v.8.0) running in a container. I have confirmed I can access the db from the host and the redshifts and AWS credentials have been verified and work perfectly (i.e. resources can be accessed as expected). When running the following command

meltano elt tap-mysql target-redshift --job_id=1

I get the below error.

ELT could not be completed: Cannot start extractor: Catalog discovery failed: command ['path/src/.meltano/extractors/tap-mysql/venv/bin/tap-mysql', '--config', 'path/src/.meltano/run/elt/1/1fab686c-b376-4e35-bb5f-0a8d0aa0565b/tap.d4ae7f81-4de6-403f-81c0-6f03613ef22a.config.json', '--discover'] returned 1
ELT could not be completed: Cannot start extractor: Catalog discovery failed: command ['path/src/.meltano/extractors/tap-mysql/venv/bin/tap-mysql', '--config', 'path/src/.meltano/run/elt/1/1fab686c-b376-4e35-bb5f-0a8d0aa0565b/tap.d4ae7f81-4de6-403f-81c0-6f03613ef22a.config.json', '--discover'] returned 1

Running

meltano select tap-mysql --list --all

also returns an error about the Catalog Discovery

Cannot list the selected attributes: Catalog discovery failed: command ['path/src/.meltano/extractors/tap-mysql/venv/bin/tap-mysql', '--config', 'path/src/.meltano/run/tap-mysql/tap.300f8f36-ab05-46f6-93b4-5c113b60b8f0.config.json', '--discover'] returned 1

I am unsure what is the cause of this error and exactly what it means. Any help would be appreciated. 🙏

Run it with meltano --log-level=debug ... and see what you get. It should show the traceback if one is generated and give more clues as to what is going on.

thank you @fred_reimer for taking the time to answer. I am getting the following error (truncated)

[....]
File "path/src/.meltano/extractors/tap-mysql/venv/lib/python3.8/site-packages/pymysql/charset.py", line 38, in by_id
    return self._by_id[id]
KeyError: 255

Github tap has an interesting issue https://github.com/transferwise/pipelinewise-tap-mysql/issues/65

Thanks @visch this did the trick for me now but i'll look into the singer variant if I need a more stable tap.

Yeah I'd say if you could at a minimum post an issue on the tap varient you're using with that fix. Ideally someone would fork the tap and upgrade pymssql. Having to manually patch pymssql is no good for production!