Github user vanzin commented on the issue: https://github.com/apache/spark/pull/17723 It would be easier if instead you said what particular API that is being proposed here you have issues with. Is it the storing of credentials in UGI? Or what? If that's what you're saying. I don't see why it's a problem to store credentials, even non-Hadoop ones, in UGI. It's just a container. Just like HDFS looks at UGI and only fetches the credentials it needs, some app blah that wants to hook up to Spark would do the same and look for its credentials there. I don't see a ton of benefits in abstracting that away into yet another security abstraction layer. And if for some reason that doesn't work, well, how do we know? Unless you have a concrete example, it's hard to develop an interface to satisfy an unknown use case.
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org