Skip to content
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.

Sign up for GitHub

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

Added note about refresh and POSIX behavior #648

Merged
merged 3 commits into from
Nov 18, 2024
+8 −1
Merged

Added note about refresh and POSIX behavior #648

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1dd5e26
Added note about refresh and POSIX behavior
rickmcgeer Nov 13, 2024
5dace0c
Update gcsfs/core.py
martindurant Nov 18, 2024
dbf839c
Update gcsfs/core.py
martindurant Nov 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion gcsfs/core.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -210,7 +210,14 @@ class GCSFileSystem(asyn.AsyncFileSystem):
GCSFileSystem maintains a per-implied-directory cache of object listings and
fulfills all object information and listing requests from cache. This implied, for example, that objects
created via other processes *will not* be visible to the GCSFileSystem until the cache
refreshed. Calls to GCSFileSystem.open and calls to GCSFile are not effected by this cache.
refreshed. Calls to GCSFileSystem.open and calls to GCSFile are not affected by this cache.

Note that directory listings are cached by default, because fetching those listings can be expensive. This is
contrary to local filesystem behaviour. The cache will be cleared if writing from this instance, but it can
martindurant marked this conversation as resolved.
Show resolved Hide resolved
become stale and return incorrect results if the storage is written to from another process/machine.
If you anticipate this possibility, you can set the use_listings_cache and listings_expiry_time arguments
to configure the caching, call `.invalidate_cache()` when required, or pass `refresh=True` to the
various listing methods.

In the default case the cache is never expired. This may be controlled via the ``cache_timeout``
GCSFileSystem parameter or via explicit calls to ``GCSFileSystem.invalidate_cache``.
Expand Down
Loading