LuciferYang opened a new issue, #14405: URL: https://github.com/apache/gravitino/issues/14405
### Version main branch ### Describe what's wrong `FilesetCatalogOperations.FileSystemCacheKey` holds the scheme, the authority and the user. For an `hdfs` path the authority comes from `HDFSFileSystemProvider.getFullAuthority`, which adds the principal without its realm and the `authentication.impersonation-enable` value, but not the authentication type. A location without a scheme has no authority at all. Schema and fileset properties can set their own authentication settings. One user's filesets can therefore share a file system built under another authentication type or a principal in another realm. For scheme-less locations, they can share one built with any other principal, keytab or impersonation setting. ### How to reproduce In one fileset catalog, create two filesets on the same HDFS cluster for the same user, one with `[email protected]` and one with `[email protected]` (or one with `authentication.type=simple` and one with `kerberos`). The second fileset reuses the first one's file system and login. -- 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]
