falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-812) all the entities must have acl
Date Thu, 16 Oct 2014 04:20:34 GMT

    [ https://issues.apache.org/jira/browse/FALCON-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173341#comment-14173341

Samarth Gupta commented on FALCON-812:

i have only used ACL in feed xmls till now, and from what i observed that the user submitting
the request , ACL owner , and the data path if exists on hdfs should all be owned by same
user. That is what this piece of code has been doing 


i have not gone through the ACL for cluster and process so not sure how that will affect the
existing set up . Also we already have ACL.OWNER and ACL.USER variables which can be passed
via merlin.properties. Can those be reused somehow ? 

> all the entities must have acl
> ------------------------------
>                 Key: FALCON-812
>                 URL: https://issues.apache.org/jira/browse/FALCON-812
>             Project: Falcon
>          Issue Type: Bug
>          Components: merlin
>    Affects Versions: 0.6
>            Reporter: Raghav Kumar Gautam
>            Assignee: Raghav Kumar Gautam
>             Fix For: 0.6
>         Attachments: falcon-812.diff
> Post falcon authorization. Once authorization is enabled, all the entities would require
acls without which all the tests are broken.

This message was sent by Atlassian JIRA

View raw message