Currently, starting a pipeline with multiple jobs queued will wait until all jobs are completed until the function exits and the console is freed up. As a result, there is no way to monitor the transfer via the API (our only current transfer monitoring happens through a progress bar on the CLI). We should implement an async start similar to the previously exposed dp.run_async() which should return a tracker (or wrapper on the tracker) to allow for transfer monitoring.
Currently, starting a pipeline with multiple jobs queued will wait until all jobs are completed until the function exits and the console is freed up. As a result, there is no way to monitor the transfer via the API (our only current transfer monitoring happens through a progress bar on the CLI). We should implement an async start similar to the previously exposed dp.run_async() which should return a tracker (or wrapper on the tracker) to allow for transfer monitoring.