[jira] [Updated] (HADOOP-14437) AdlFileSystem.getAclStatus() returns unexpected ACL information
[ https://issues.apache.org/jira/browse/HADOOP-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated HADOOP-14437: Issue Type: Sub-task (was: Bug) Parent: HADOOP-14764 > AdlFileSystem.getAclStatus() returns unexpected ACL information > --- > > Key: HADOOP-14437 > URL: https://issues.apache.org/jira/browse/HADOOP-14437 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/adl >Reporter: Sailesh Mukil > Labels: acl, api-breaking > > The HDFS getAclStatus() returns ACL information of a file and how that > pertains to a Hadoop user/group. > However, the ADLS getAclStatus() returns ACL information of a file but does > not map them to Hadoop users/groups and instead maps them to the client ID of > the SPI. > The components built around Hadoop use this API with the expectation that the > ACL information returned will be mapped to Hadoop users/groups, i.e. the > components expect it to have the same behavior as other filesystems that > support this API. > If not, the components need to have logic to handle this case where if > they're talking to ADLS, they won't look for matching the Hadoop user/group, > but instead the client ID. And once AdlFileSystem changes its API to be able > to map to Hadoop users/groups, it will be a breaking change for all the > components. > Until such functionality is able to be provided, I would suggest that the > getAclStatus() be unsupported, just as it is in S3AFileSystem. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-14437) AdlFileSystem.getAclStatus() returns unexpected ACL information
[ https://issues.apache.org/jira/browse/HADOOP-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Zhuge updated HADOOP-14437: Hadoop Flags: Incompatible change > AdlFileSystem.getAclStatus() returns unexpected ACL information > --- > > Key: HADOOP-14437 > URL: https://issues.apache.org/jira/browse/HADOOP-14437 > Project: Hadoop Common > Issue Type: Bug > Components: fs/adl >Reporter: Sailesh Mukil > Labels: acl, api-breaking > > The HDFS getAclStatus() returns ACL information of a file and how that > pertains to a Hadoop user/group. > However, the ADLS getAclStatus() returns ACL information of a file but does > not map them to Hadoop users/groups and instead maps them to the client ID of > the SPI. > The components built around Hadoop use this API with the expectation that the > ACL information returned will be mapped to Hadoop users/groups, i.e. the > components expect it to have the same behavior as other filesystems that > support this API. > If not, the components need to have logic to handle this case where if > they're talking to ADLS, they won't look for matching the Hadoop user/group, > but instead the client ID. And once AdlFileSystem changes its API to be able > to map to Hadoop users/groups, it will be a breaking change for all the > components. > Until such functionality is able to be provided, I would suggest that the > getAclStatus() be unsupported, just as it is in S3AFileSystem. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
