Hello everyone! We are using meltano on kubernetes environment and we want to export some tables to CSV files. We are working with a simple ELT (tap-mysql -> target-csv). It works well and this makes me very happy: D. In doing the various tests we noticed that the tables are parallelly exported but we had never noticed this behavior before, but only a sequential mode. Does this behavior depend on the particular environment (kubernetes) or is it a Meltano feature? Is it possible to set a maximum number of tables that can be processed in parallel or does it scale according to the available resources?

I'm pretty sure it's a tap-mysql feature!

@gentle-minister-47752 Which specific tap-mysql are you using? https://github.com/transferwise/pipelinewise-tap-mysql as documented on https://meltano.com/plugins/extractors/mysql.html? Extracting data is entirely the tap's responsibility, with Meltano only handling the execution environment of the tap, so as Derek says, any specific extraction behavior you're seeing is necessarily a feature of the tap. Meltano doesn't know how to tell taps to run sequentially or in parallel (since there's no generic way that would work for all taps), and it doesn't detect whether it's running inside Kubernetes, so the tap must be using some heuristics of its own!

We are using this "https://github.com/singer-io/tap-mysql/".

All right, I'm not immediately seeing code suggesting it extracts tables in parallel. What indications were you seeing that it was?

We noticed that when we were testing on a single server, csv files were created one after each other

Interesting! The answer has to be somewhere in https://github.com/singer-io/tap-mysql but I'm not seeing it yet. Perhaps it's behaving differently with different sync strategies (https://github.com/singer-io/tap-mysql/tree/master/tap_mysql/sync_strategies), and you were using one locally and another in prod?

We are using full table sync strategy locally and in prod. we will look deeper into 😉 Anyway, thank you both for your your reply.