You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Anuj Modi (Jira)" <ji...@apache.org> on 2024/03/01 05:05:00 UTC
[jira] [Updated] (HADOOP-19089) [ABFS] Reverting Back Support of setXAttr() and getXAttr() on root path
[ https://issues.apache.org/jira/browse/HADOOP-19089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anuj Modi updated HADOOP-19089:
-------------------------------
Affects Version/s: 3.4.1
> [ABFS] Reverting Back Support of setXAttr() and getXAttr() on root path
> -----------------------------------------------------------------------
>
> Key: HADOOP-19089
> URL: https://issues.apache.org/jira/browse/HADOOP-19089
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.4.0, 3.4.1
> Reporter: Anuj Modi
> Assignee: Anuj Modi
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> A while back changes were made to support HDFS.setXAttr() and HDFS.getXAttr() on root path for ABFS Driver.
> For these, filesystem level APIs were introduced and used to set/get metadata of container.
> Refer to Jira: [HADOOP-18869] ABFS: Fixing Behavior of a File System APIs on root path - ASF JIRA (apache.org)
> Ideally, same set of APIs should be used, and root should be treated as a path like any other path.
> This change is to avoid calling container APIs for these HDFS calls.
> As a result of this these APIs will fail on root path (as earlier) because service does not support get/set of user properties on root path.
> This change will also update the documentation to reflect that these operations are not supported on root path.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org