thswlsqls opened a new issue, #8556: URL: https://github.com/apache/paimon/issues/8556
**Search before asking** - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. **Paimon version** master @ a8e4069b9 **Compute Engine** Engine-agnostic (core) — surfaces on any engine reading file status over GCS. **Minimal reproduce step** Read file status through `GSFileIO` on a GCS path, e.g. `fileIO.getFileStatus(path)`, and inspect `getAccessTime()` and `getOwner()`. `HadoopCompliantFileIO.HadoopFileStatus` (paimon-filesystems/paimon-gs-impl/.../gs/HadoopCompliantFileIO.java line 262) overrides only `getLen`/`isDir`/`getPath`/`getModificationTime`. It does not override `getAccessTime()`/`getOwner()`, so the `FileStatus` interface defaults apply: `getAccessTime()` returns `0` and `getOwner()` returns `null`, even though the wrapped `org.apache.hadoop.fs.FileStatus` carries the real values. The delegation is the established pattern in every other Hadoop-compliant FS impl (s3/oss/obs/cosn/azure). It originated in core `HadoopFileIO`+s3+oss (#4459) and was added per-module for obs/cosn/azure; the GS impl introduced later by #5238 omitted it. **What doesn't meet your expectations?** On GCS, file access time is always `0` and owner is always `null`, diverging from all other object-store filesystems, which return the actual values. **Anything else?** N/A **Are you willing to submit a PR?** - [x] I'm willing to submit a PR! --- -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
