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

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

                Author: ASF GitHub Bot
            Created on: 01/Jun/24 02:19
            Start Date: 01/Jun/24 02:19
    Worklog Time Spent: 10m 
      Work Description: arjun4084346 commented on code in PR #3955:
URL: https://github.com/apache/gobblin/pull/3955#discussion_r1623096103


##########
gobblin-data-management/src/main/java/org/apache/gobblin/data/management/copy/ManifestBasedDataset.java:
##########
@@ -132,9 +132,10 @@ public Iterator<FileSet<CopyEntity>> 
getFileSetIterator(FileSystem targetFs, Cop
             copyableFile.setFsDatasets(srcFs, targetFs);
             copyEntities.add(copyableFile);
 
-            Path fromPath = srcFs.getFileStatus(fileToCopy).isDirectory() ? 
fileToCopy : fileToCopy.getParent();
+            // Always grab the parent since the above permission setting 
should be setting the permission for a folder itself

Review Comment:
   can you add to the comment more details why we need/can skip the last dir, 
and also comment about these permissions being set in other place.
   





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

    Worklog Id:     (was: 921608)
    Time Spent: 1h 20m  (was: 1h 10m)

> Permission mismatch in manifest distcp where empty folders are copied
> ---------------------------------------------------------------------
>
>                 Key: GOBBLIN-2072
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2072
>             Project: Apache Gobblin
>          Issue Type: Bug
>          Components: gobblin-core
>            Reporter: William Lo
>            Assignee: Abhishek Tiwari
>            Priority: Minor
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> In Manifest distcp, empty folders are being set with the incorrect 
> permissions in SetPermissionStep after being correctly set in the 
> CopyDataPublisher.
> The suspected reason is that the folders themselves are being treated as 
> ancestors, and this causes the permission checking of the source and 
> destination ancestors to act incorrectly. TODO: We should consolidate our 
> permission comparison and logic given that there are a multitude of different 
> implementations and they each seem to have their own quirks.
> Correct CopyDataPublisher:
> {code:java}
> Setting destination directory hdfs://cluster/a/b/c owner and permission to 
> rwxr-x---{code}
> Incorrect permission commit step:
> {code:java}
> [Azkaban] Setting permission rwxr-xr-x on path /a/b/c{code}



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

Reply via email to