mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[PR #2675] [MERGED] Refactor StatCache words from NoObject to Negative #2700
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#2700
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/2675
Author: @ggtakec
Created: 5/31/2025
Status: ✅ Merged
Merged: 6/10/2025
Merged by: @gaul
Base:
master← Head:stat/02_negative📝 Commits (1)
fb60942Refactor StatCache words from NoObject to Negative📊 Changes
5 files changed (+47 additions, -32 deletions)
View changed files
📝
doc/man/s3fs.1.in(+13 -7)📝
src/cache.cpp(+7 -7)📝
src/cache.h(+8 -8)📝
src/s3fs.cpp(+5 -5)📝
src/s3fs_help.cpp(+14 -5)📄 Description
Relevant Issue (if applicable)
#2674
Details
This PR is Phase 2 of fixes to refactor and improve StatCache.
(Draft until #2674 is merged. Subsequent PRs will follow based on this PR codes.)
The word
NoObjectCachehas been changed toNegativeCachebecause its meaning is ambiguous and misleading.We should distinguish clearly within s3fs between the case where the object (file) does not exist and the case where the object does not exist as a directory path but a child object does, so we are changing it to the word
Negative.In conjunction with this, we are also changing the name of the existing option
disable_noobj_cachetodisable_negative_cache.The old option will be deprecated, but will continue to be supported.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.