[
https://issues.apache.org/jira/browse/RANGER-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated RANGER-3599:
--------------------------------
Description:
Behavior for chmod and chown should be consistent when fallback to hadoop acl
is not enabled.
Currently even though the user is the owner of the file, chmod is not allowing
the user to change the permission when fallback to hadoop ACL is not enabled.
Also "chown" should behave the same way like what is there when hadoop acl is
enabled.
This is follow up patch for https://issues.apache.org/jira/browse/RANGER-3148
issue.
was:
Behavior for chmod and chown should be consistent when fallback to hadoop acl
is not enabled.
Currently even though the user is the owner of the file, chmod is not allowing
the user to change the permission when fallback to hadoop ACL is not enabled.
Also "chown" should behave the same way like what is there when hadoop acl is
enabled.
> Behavior of chmod and chown should be consistent when fallback to hadoop acl
> is not enabled
> -------------------------------------------------------------------------------------------
>
> Key: RANGER-3599
> URL: https://issues.apache.org/jira/browse/RANGER-3599
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Ramesh Mani
> Assignee: Ramesh Mani
> Priority: Minor
>
> Behavior for chmod and chown should be consistent when fallback to hadoop acl
> is not enabled.
> Currently even though the user is the owner of the file, chmod is not
> allowing the user to change the permission when fallback to hadoop ACL is not
> enabled.
> Also "chown" should behave the same way like what is there when hadoop acl is
> enabled.
> This is follow up patch for
> https://issues.apache.org/jira/browse/RANGER-3148 issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
