Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/21548
> I just have an issue with your summary. It makes it sound like there's no
way to securely configure these things today, and that's not true.
>
> You can have the password in the config file and have it only readable by
authorized users, which is basically what the credential provider does.
>
> Or you can have the password in an env variable, and reference the env
variable in the Spark config.
I see, thanks for explanation @vanzin . This might be the problem in our
distribution, because we don't do such fine-grained access control of config
file, also configuration file is world readable shared between different
components, that's why we're seeking to use Hadoop credential provide to secure
this thing.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
