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

Siyao Meng resolved HDDS-1939.
------------------------------
    Resolution: Not A Problem

Turns out this problem goes away as a side effect of HDDS-3501 by [~elek]:

https://github.com/apache/hadoop-ozone/commit/6fb2b3e3726284a41a20b5bc91387457f9625f33#diff-69498beacfd2dce93095ab6cd74e0571R459-R460

This was a problem because before HDDS-3501, OzoneFileStatus extends FileStatus 
but the former doesn't really store owner and group information. As a result, 
{{status.getOwner()}} retrieves 
[{{null}}|https://github.com/apache/hadoop/blob/fb8932a727f757b2e9c1c61a18145878d0eb77bd/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileStatus.java#L54-L55].

As of now with HDDS-3501, owner and group field of FileStatus from o3fs will be 
[populated|https://github.com/apache/hadoop-ozone/blob/ffb340e32460ccaa2eae557f0bb71fb90d7ebc7a/hadoop-ozone/ozonefs/src/main/java/org/apache/hadoop/fs/ozone/BasicOzoneFileSystem.java#L171-L176]
 with the current userName.

Resolving this jira.

> Owner/group information for a file should be returned from OzoneFileStatus
> --------------------------------------------------------------------------
>
>                 Key: HDDS-1939
>                 URL: https://issues.apache.org/jira/browse/HDDS-1939
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Filesystem, Security
>    Affects Versions: 0.4.0
>            Reporter: Mukul Kumar Singh
>            Assignee: Siyao Meng
>            Priority: Critical
>              Labels: Triaged
>
> BasicOzoneFilesystem returns the file's user/group information as the current 
> user/group. This should default to the information read from the acl's for 
> the file.
> cc [~xyao]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to