Hi, <the default mysql extractor extractor> is fro...
# singer-tap-development
m
Hi, the default mysql extractor extractor is from wise, but as far as I understand, we cannot modify it easily, because pipelinewise now maintains a single repository of all taps. On the other hand, we have https://github.com/MeltanoLabs/tap-mysql, but how incremental or log-based replication is configured or modified? Or is it still needs to be developed?
e
we cannot modify it easily, because pipelinewise now maintains a single repository of all taps
It's really no more complicated than modifying any other tap, just fork it, make your changes and update the
pip_url
. The only difference is you need to add a
subdirectory
fragment to the git URI: https://github.com/meltano/hub/blob/83d73212cab51a6c8d038db7757421629c663433/_data/meltano/extractors/tap-mysql/transferwise.yml#L17C63-L17C75
On the other hand, we have https://github.com/MeltanoLabs/tap-mysql, but how incremental or log-based replication is configured or modified? Or is it still needs to be developed?
I've been somewhat distant from the development of this tap, but I don't think log-based replication is currently supported, but issues and PRs are always welcome.
m
Thanks for sharing those details. If I need log-based replication that is compatible with 8.4 mysql. Would you suggest forking pipelinewise or developing the feature in meltanolabs version? https://dev.mysql.com/doc/refman/8.4/en/show-master-status.html
e
I'd selfishly prefer adding it to the meltanolabs variant, and I can help with reviewing the PR and figuring out the CI once it's up, but I don't the know how the level of effort compares between one and the other
😄 1
👍 1