This is a question on Meltano Extractor for MySQL ...
# singer-taps
b
This is a question on Meltano Extractor for MySQL Currently we are heavy MySQL Store and have our Taps/Extractors used for MySQL But I recently came across this notice https://github.com/transferwise/pipelinewise-tap-mysql?tab=readme-ov-file#notice Historically MySQL Taps have been seeing low interest in Meltano community and Pipelinewise was a savior, but in the light of above notice, does anybody know if pipelinewise-mysql is surviving this "shrinkage" What are the other alternatives that are at feature parity with pipelinewise ? We're relying on LOG replication functionality for replication
e
Hi @binoy_shah! Thanks for sharing that notice! I don't see a mention there about removing or yanking PyPI releases for the Singer connectors, so as long as you use https://pypi.org/project/pipelinewise-tap-mysql/, you should be good. Even the GitHub repo I hope is not going anywhere. All this means that probably the existing connector repos will not get updates, and there won't be new releases to PyPI. For tap-mysql in particular, it seems they're still relying on the PyPI package so I'm not completely sure what changes are already taking place: https://github.com/transferwise/pipelinewise/blob/af612017ad5bf33b92fc4806c961c798c3e9e469/singer-connectors/tap-mysql/requirements.txt.
b
Thanks for the update @Edgar Ramírez (Arch.dev)
d
hi @binoy_shah, about the log replication how are you handling the missing binary log files error. after some time the binary_log file gets deleted by the mysql itself and the transfer state is set to use those deleted binary files. how are you handling these issues ?