thswlsqls opened a new issue, #8815: URL: https://github.com/apache/paimon/issues/8815
**Search before asking** - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. **Paimon version** master @ d3b62affb **Compute Engine** Engine-agnostic (Azure FileIO adapter) **Minimal reproduce step** Use a single `AzureFileIO` instance to access paths under two different authorities (e.g. `abfs://[email protected]/...` and `abfs://[email protected]/...`). `HadoopCompliantFileIO.getFileSystem()` (`paimon-filesystems/paimon-azure-impl/.../azure/HadoopCompliantFileIO.java` line 44, 109) caches the first authority's `FileSystem` in a single instance field `fs` and returns it regardless of the requested authority. The sibling oss/s3/gs/obs (#8589) already cache by authority in a `Map<String, FileSystem>`. **What doesn't meet your expectations?** Expected: each authority is served by its own `FileSystem`. Actual: after the first access, all read/write/delete/rename for other authorities are misrouted to the first authority's `FileSystem`, causing silent reads/writes against the wrong storage account. **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]
