Github user mgummelt commented on the issue: https://github.com/apache/spark/pull/17723 I'm working on this now, and am definitely willing to execute the plan we've agreed on, but the more I think about it, the more I think it makes sense to make `ServiceCredentialProvider` private and not pluggable. The benefit is that we don't have to design a possibly incorrect delegation token interface until we actually have another implementation to design against. The cost is that Mesos users would not be able to provide their own delegation token implementations. However, YARN users still would, since the `yarn.ServiceCredentialProvider` would still exist. I would remove the deprecation. @vanzin @mridulm Does this work for both of you? We briefly considered this at the beginning of this PR conversation, and I think both of you suggested it's acceptable. Out of curiousity, what was the benefit of making delegation token provision pluggable in the first place? What other Hadoop delegation token providers other than HDFS, HBase, and Hive are there? What was the be
--- 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