Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 23 Sep 2014 20:35:35 +0000 (UTC)
From: "Zhijie Shen (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12716465.1400885424000.106798.1411504535354@Atlassian.JIRA>
In-Reply-To: <JIRA.12716465.1400885424000@Atlassian.JIRA>
References: <JIRA.12716465.1400885424000@Atlassian.JIRA>
 <JIRA.12716465.1400885424275@arcas>
Subject: [jira] [Commented] (YARN-2102) More generalized timeline ACLs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145390#comment-14145390 ] 

Zhijie Shen commented on YARN-2102:
-----------------------------------

[~vinodkv], thanks for the comments. I've addressed them in the new patch. In addition, I've fixed a client bug together.

> More generalized timeline ACLs
> ------------------------------
>
>                 Key: YARN-2102
>                 URL: https://issues.apache.org/jira/browse/YARN-2102
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>         Attachments: GeneralizedTimelineACLs.pdf, YARN-2102.1.patch, YARN-2102.2.patch, YARN-2102.3.patch, YARN-2102.5.patch, YARN-2102.6.patch, YARN-2102.7.patch
>
>
> We need to differentiate the access controls of reading and writing operations, and we need to think about cross-entity access control. For example, if we are executing a workflow of MR jobs, which writing the timeline data of this workflow, we don't want other user to pollute the timeline data of the workflow by putting something under it.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)