-
Notifications
You must be signed in to change notification settings - Fork 4
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
fsspec-cache-clear: add config variables for clearing cache up #31
Comments
@yarikoptic While fsspec has the necessary pieces to implement such a cleanup in datalad-fuse, the code would end up relying largely on undocumented implementation details of how fsspec structures its cache metadata. Are you sure that's the best idea? |
I agree that we must not implement something based on some undocumented implementation details. I think then an issue (or better a PR) should be filed with fsspec to expose (and documenting) interface(s) to provide such functionality. In the minimalistic case it could be some |
@yarikoptic Issue created: fsspec/filesystem_spec#857 |
ATM the entire cache is cleaned up by the command.
age
(oratime_age
, as in "last accessed", not when was created), andsize
limits, so we could keep caches "under control".datalad.fsspec.cache-clear.age
anddatalad.fsspec.cache-clear.size
which would default toNone
(not considered)only_in_file_tree
to remove cached items which are no longer available in the currentgit
(annex) file tree (of current commit). But 1). I do not think it would be easily possible without adding some extra layer of tracking; 2). such items would eventually could be picked up throughage
. So, let's not bother about this oneThe text was updated successfully, but these errors were encountered: