Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17723
@mridulm the main argument for just dealing with Hadoop security is that
it's been sufficient since the inception of Spark. I have never seen anyone ask
for integration with any other type of system. Most of the non-Hadoop systems
supported by Spark don't need this kind of functionality (e.g. S3 just uses
secrets stored in configuration or a credential store - both of which are
handled by the Hadoop libraries btw, not Spark).
That being said, I think this whole discussion is distracting from the main
goal of the change, which is to expose *Hadoop*-based security in Mesos-based
applications. Would it make you more comfortable if the new API were kept
`private[spark]`? It would limit extensibility in the case of Mesos (would be
restricted to built-in providers), but would free us from this discussion and
allow progress to happen.
Really, personally, unless someone can given me a concrete example, I don't
see a pressing need to have a lengthy discussion about non-Hadoop-based
security frameworks.
---
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
