Dmitry Petrov

> we'd have to download (stream) the data, defeating (imo) the purpose of having a `--no-download` flag. Yes, not spending time for the download is the core requirement here. I...

> At the moment, the chunking is crucial for further usage of dvc. We are going to automate our MLOps pipeline which will update dataset of approx. @Chickenmarkus I'd appreciate...

@Chickenmarkus a feedback to your setup is below: **First,** `Update the label of an existing record` can be a root cause of multiple issues. Data and labels have a different...

@efiop you explained that the first case is not correct. Could you please clarify with the second one - does DVC works properly and should we close this issue?

I like the idea of `dvc pull --dir-only` - it can bring the entire dir structure, help users to navigate in the dir and simplify API as a result. `--merge-into`...

@tbugfinder it is a great question! We are trying figure out the priorities. Please create an issue for Jenkins if it is important for you. @barseghyanartur is right - it...

@elleobrien should we close this issue?

We also need to pull metrics (data files) when a job is running

Actually, I'm not sure about `refresh`. It might be better to sync status & logs as part of `refresh` and sync data with another command. @DavidGOrtega could you please clarify...

> 1. Use ephemeral buckets for every task and delete them as soon as users harvest the results Please note, `ephemeral buckets` means an actual bucket (not a key/path in...