-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make dvc pull --run-cache
allow targets
for a granular pull process
#4223
Comments
For the record: |
Oh, ok. Is there any kind of estimative on this being prioritized? As described in the forum, I was planning to use |
Hi @maricatovictor ! Sorry for the delay. We've added this task to the next sprint (starting next week). |
Existing lock files are just an edge case of run-cache. Prerequisite for iterative#4223
Existing lock files are just an edge case of run-cache. Prerequisite for #4223
This option allows run-cache to pull the cache for the outputs when restoring a stage instead of pulling everything at once during `dvc pull --run-cache`. Fixes iterative#4223
* repro: support --pull This option allows run-cache to pull the cache for the outputs when restoring a stage instead of pulling everything at once during `dvc pull --run-cache`. Fixes #4223 * repro: adjust --pull help
Right now, if I do
dvc pull [target]
this will pull only the
target
I am interested in.However, if I do
dvc pull --run-cache [targets]
the
target
is ignored, everything is pulled from remote. Not even a warning is thrown that--run-cache
does not accept granularly pulling files.This is based on https://discuss.dvc.org/t/dvc-pull-run-cache-target/444 discussion
The text was updated successfully, but these errors were encountered: