Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HADOOP-16005: Add XAttr support to WASB and ABFS #452

Open
wants to merge 6 commits into
base: trunk
from

Conversation

Projects
None yet
2 participants
@c-w
Copy link
Member

commented Dec 22, 2018

As discussed in HADOOP-16005, this pull request implements getXAttr and setXAttr on hadoop-azure's WASB and ABFS file-systems.

The changes were tested against the following Azure storage account configurations:

  • WASB: StorageV2, RA-GRS replication in East US (primary) West US (secondary). WASB test session screenshot. All tests pass and the ABFS tests are skipped as expected.

  • ABFS: StorageV2 with Data Lake Storage Gen2 preview enabled, RA-GRS replication in East US (primary) West US (secondary). ABFS test session screenshot. All ABFS tests pass but the WASB tests fail since the storage account hasn't implemented the blob endpoints yet.

The test-patch script passed: test-patch output.

@c-w c-w force-pushed the CatalystCode:hadoop-16005 branch from 1c8303a to 8774393 Dec 22, 2018

c-w added some commits Feb 5, 2019

Rename name to xAttrName
This helps differentiate the variable from the key variable.
Remove unnecessary check
Both xns (namespace enabled) account and non-xns support set/getAttr.
Remove unnecessary check
Both xns (namespace enabled) account and non-xns support set/getAttr.
Rename name to xAttrName
This helps differentiate the variable from the key variable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.