[
https://issues.apache.org/jira/browse/MAPREDUCE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834120#action_12834120
]
Vinod K V commented on MAPREDUCE-1455:
--------------------------------------
bq. Does it make sense to have the info in the log.info file that is already
there in the task logs directory?
This isn't much different from writing a separate file in attempt directory
except in the number of files per attempt. In both the approaches, there is a
duplication of ACLs information across various tasks of the same job.
MAPREDUCE-927 is planning to change the logs directory structure from
{{userlogs/$attemptid}} to {{userlogs/$jobid/$attemptid}}. Once that is done,
we can simply write one ACL file per job in the {{userlogs/$jobid}} directory.
This will avoid the duplication of information and can be done. Unless we are
really very concerned about adding a new file per job after MAPREDUCE-927.
> Authorization for servlets
> --------------------------
>
> Key: MAPREDUCE-1455
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1455
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: jobtracker, security, tasktracker
> Reporter: Devaraj Das
> Assignee: Ravi Gummadi
> Fix For: 0.22.0
>
>
> This jira is about building the authorization for servlets (on top of
> MAPREDUCE-1307). That is, the JobTracker/TaskTracker runs authorization
> checks on web requests based on the configured job permissions. For e.g., if
> the job permission is 600, then no one except the authenticated user can look
> at the job details via the browser. The authenticated user in the servlet can
> be obtained using the HttpServletRequest method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
