-
Notifications
You must be signed in to change notification settings - Fork 1.2k
dvc get from subdir #2847
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
Comments
It seems like it is not a regression. It fails only on data dirs, not in data files in a regular dir (which worked):
I'm removing high-pri tag. |
@dmpetrov is dataset public to reproduce? It looks like I don't have access to it. |
If I get it right. Yes, I think it was never implemented. DVC in general never provided file-level granularity for directories. E.g. you can't So, I would consider this as a feature request. That makes sense to me, even though would be the first time we go to intra-directory level of data management with DVC. Initial implementation would be inefficient due to the reasons I described - we don't have a mean to fetch into cache a single file for a directory. Also, should we support subdirectories? wildcards? any other considerations? |
Related #2458 |
Closing as a duplicate of #2458 |
Uh oh!
There was an error while loading. Please reload this page.
Regular
pull
works just fine for subdirs:dvc get
does not work:This is quite a basic scenario - high priority bug.
EDITED: It worked before - regression.
The text was updated successfully, but these errors were encountered: