[
https://issues.apache.org/jira/browse/MAPREDUCE-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861364#action_12861364
]
Vinod K V commented on MAPREDUCE-1604:
--------------------------------------
I agree with your comments about documentation being part of the whole.
My only problem here is Job-acls ARE an unstable feature. The moment one
configures job-acls to be used, issues like MAPREDUCE-1664 crop up. Also if
MAPREDUCE-1664 doesn't go in 0.21, we will need to support
_job-authorization.enabled_ flag in 0.22 as it is going away in favour of
mapred-acls-enabled flag.
I am just trying to see if we should remove the documentation of this feature
for release 0.21 and get the complete feature in for 0.22. I am not sure of any
process via which we can tell users about known issues. Even if we have one,
I'd rather prefer turning off this feature completely in 0.21 as without
MAPREDUCE-1664 and related issues, this issue is practically useless. What do
you think about it?
> Job acls should be documented in forrest.
> -----------------------------------------
>
> Key: MAPREDUCE-1604
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1604
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: documentation, security
> Affects Versions: 0.22.0
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.22.0
>
> Attachments: patch-1604-1.txt, patch-1604-ydist.txt, patch-1604.txt
>
>
> Job acls introduced in MAPREDUCE-1307 should be documented in forrest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
