Github user alpivonka commented on the pull request:
https://github.com/apache/spark/pull/5325#issuecomment-173561257
I would like to bring up an opportunity for re-use.
with in the mapred-site.xml (for our implementation) we are using the
following to allow access to mapreduce logs ...etc..
Why reinvent the wheel, most often the users/groups for both MR and Spark
would be the some or all of the same user/groups.
My suggestion is to create a common list/set of properties between MR and
Spark for acls. Instead of maintaining two separate lists
mapreduce.cluster.acls.enabled = true
mapreduce.job.acl-view-job=mapred,hue,* <group name>
mapreduce.job.acl-modify-job=mapred,hue,* <group name>
---
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
