[ 
https://issues.apache.org/jira/browse/GOBBLIN-2009?focusedWorklogId=907698&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-907698
 ]

ASF GitHub Bot logged work on GOBBLIN-2009:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/Mar/24 00:15
            Start Date: 01/Mar/24 00:15
    Worklog Time Spent: 10m 
      Work Description: arjun4084346 opened a new pull request, #3887:
URL: https://github.com/apache/gobblin/pull/3887

   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I 
have checked off all the steps below!
   
   
   ### JIRA
   - [x] My PR addresses the following [Gobblin 
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references 
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-2009
   
   
   ### Description
   - [x] Here are some details about my PR, including screenshots (if 
applicable):
   From my observation, setting an ACL may change the file permission if it is 
not the same as permission. But changing permission does not change the ACLs; 
it may update the mask value which changes the effective permission of the ACL 
entry though.
   Thus in order to achieve same ACL and same permission in destination as 
source, we should first apply ACLs and then apply permissions.
   
   ```
   hdfs dfs -ls /tmp/x3
   -rw-rwxr

Issue Time Tracking
-------------------

            Worklog Id:     (was: 907698)
    Remaining Estimate: 0h
            Time Spent: 10m

> setting acls change the final permission of the file
> ----------------------------------------------------
>
>                 Key: GOBBLIN-2009
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2009
>             Project: Apache Gobblin
>          Issue Type: Bug
>            Reporter: Arjun Singh Bora
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to