You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: hadoop-tools/hadoop-azure/src/site/markdown/index.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1469,7 +1469,12 @@ Once the above properties are configured, `hdfs dfs -ls abfs://container1@abfswa
1469
1469
1470
1470
Following failures are known and expected to fail as of now.
1471
1471
1. AzureBlobFileSystem.setXAttr() and AzureBlobFileSystem.getXAttr() will fail when attempted on root ("/") path with `Operation failed: "The request URI is invalid.", HTTP 400 Bad Request`
1472
-
1472
+
2. If you're using user-delegation SAS authentication:
1473
+
- Listing operation for HNS accounts (on DFS endpoint) works with SAS token supporting either blob or directory
1474
+
scopes (Signed Resource Type as Blob or Directory),
1475
+
though it is intended to work only at the directory scope. It is a known bug.
1476
+
- AzureBlobFileSystem.getFileStatus() is expected to fail at root ("/") path with
1477
+
`Operation failed: "Server failed to authenticate the request.", HTTP 401 Unauthorized Error`
1473
1478
## <aname="testing"></a> Testing ABFS
1474
1479
1475
1480
See the relevant section in [Testing Azure](testing_azure.html).
0 commit comments