Consistent symlink handling across GCS clients
GCSFuse now represents symbolic links the same way as Storage Transfer Service (STS) and other GCS clients(like gcloud storage CLI etc). This feature makes it easier for customers to transfer data via GCSFuse to and from GCS without worrying about symbolic link compatibility issues across GCS clients. This is enabled by default.
GCSfuse will now represent the symbolic links as finite-sized objects where the content is the target path, identified by the reserved metadata goog-reserved-file-is-symlink: true. This new feature is compatible with old representation of symbolic links used by prior versions of GCSFuse.
Bug fixes & Improvements
- Enhanced resiliency of the writes(that includes checkpoint write) by increasing the retry deadline to a higher value(120s instead of 32s) PR#4473.
- Fixed a bug in the requester pays feature to ensure the billing project correctly propagates for ListObject requests in gRPC protocol, eliminating the "no user project provided" error PR#4611
- File Cache now adheres to the physical space utilization of files on the storage media rather than logical size PR#4514
- Fixed memory leak in buffered reader during multi-block read PR#4638
Improved direct patch enforcement strategy for gRPC client PR#4635