[ 
https://issues.apache.org/jira/browse/MAPREDUCE-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vinod K V updated MAPREDUCE-1747:
---------------------------------

    Attachment: MAPREDUCE-1747-20100504.txt

I did sanity tests as suggested by Ravi with two queues. The machinery is all 
well-oiled. Will resubmit it to Hudson one more time just to be sure.

> Remove documentation for the 'unstable' job-acls feature
> --------------------------------------------------------
>
>                 Key: MAPREDUCE-1747
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1747
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 0.21.0
>            Reporter: Vinod K V
>            Assignee: Vinod K V
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: MAPREDUCE-1747-20100420.txt, MAPREDUCE-1747-20100504.txt
>
>
> As discussed 
> [here|https://issues.apache.org/jira/browse/MAPREDUCE-1604?focusedCommentId=12862151&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12862151]
>  and 
> [here|https://issues.apache.org/jira/browse/MAPREDUCE-1604?focusedCommentId=12860916&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12860916]
>  at MAPREDUCE-1604, the job-acls feature is currently unstable. Without 
> MAPREDUCE-1664, job-acls are practically useless because of their problematic 
> interactions with queue-acls. Removing them for 0.21 will both relieve 
> ourselves of these problems as well as the burden to support the backwards 
> compatibility of the configuration options as well as the going-to-be-changed 
> semantics of the feature. This jira is about removing the documentation from 
> 0.21 so that the completed feature can be added in 0.22 with ease.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to