thswlsqls opened a new issue, #8953: URL: https://github.com/apache/paimon/issues/8953
**Search before asking** - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. **Paimon version** master @ 8cd760d64 **Compute Engine** Engine-agnostic (core) — surfaces on any engine reading file status over OSS. **Minimal reproduce step** Read file status through `JindoFileIO` on an `oss://` path, e.g. `fileIO.getFileStatus(path)`, and inspect `getAccessTime()` and `getOwner()`. `HadoopCompliantFileIO.HadoopFileStatus` (paimon-filesystems/paimon-jindo/.../jindo/HadoopCompliantFileIO.java line 409) overrides only `getLen`/`isDir`/`getPath`/`getModificationTime`. It does not override `getAccessTime()`/`getOwner()`, so the `FileStatus` interface defaults apply — `0` and `null` — even though the wrapped `org.apache.hadoop.fs.FileStatus` carries the real values. Every other Hadoop-compliant FS impl (s3/oss/obs/cosn/azure/gs) delegates both getters. The gs impl was fixed by #8559; paimon-jindo is the last one left. **What doesn't meet your expectations?** Object table queries expose this directly: `ObjectTableImpl.toRow()` fills the `atime` and `owner` columns from these getters, so both are always `0`/`NULL` over Jindo. **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]
