hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-2102) More generalized timeline ACLs
Date Sat, 23 Aug 2014 06:15:11 GMT

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

Zhijie Shen updated YARN-2102:
------------------------------

    Attachment: YARN-2102.1.patch

I divided the work into two halves. In this Jira, I'd like to scope the work within  defining
TimelineNamespace data model, reading from and writing into timeline store, making REST APIs
for users to operate on the namespace and TimelineClient wrapper over the PUT method. In other
word, this Jira focuses on making the new TimelineNamespace work end to end.

I'll create a follow up Jira to use TimelineNamespace to protect entities.

> 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
>
>
> 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.2#6252)

Mime
View raw message