Description
Uber-JIRA for wasb:// phase II: the things we want for Hadoop 2.9.
I think the focus is on performance, but looking at the tests there are some things we need there first: parallel test execution, move over to IT tests, other tuning.
All patches must come with declarations of which azure endpoint they were tested against.
Attachments
Issue Links
- depends upon
-
HADOOP-14547 [WASB] the configured retry policy is not used for all storage operations.
- Resolved
-
HADOOP-14518 Customize User-Agent header sent in HTTP/HTTPS requests by WASB.
- Resolved
-
HADOOP-14461 Azure: handle failure gracefully in case of missing account access key
- Resolved
-
HADOOP-14478 Optimize NativeAzureFsInputStream for positional reads
- Resolved
-
HADOOP-14581 Restrict setOwner to list of user when security is enabled in wasb
- Resolved
-
HADOOP-14598 Blacklist Http/HttpsFileSystem in FsUrlStreamHandlerFactory
- Resolved
-
HADOOP-14443 Azure: Support retry and client side failover for authorization, SASKey and delegation token generation
- Resolved
-
HADOOP-14520 WASB: Block compaction for Azure Block Blobs
- Resolved
-
HADOOP-14535 wasb: implement high-performance random access and seek of block blobs
- Resolved
-
HADOOP-14536 Update azure-storage sdk to version 5.3.0
- Resolved
- is superceded by
-
HADOOP-15132 Über-jira: WASB client phase III: roll-up for Hadoop 3.2
- Open
- relates to
-
HADOOP-14478 Optimize NativeAzureFsInputStream for positional reads
- Resolved
-
HADOOP-14680 Azure: IndexOutOfBoundsException in BlockBlobInputStream
- Resolved
-
HADOOP-15042 Azure PageBlobInputStream.skip() can return negative value when numberOfPagesRemaining is 0
- Resolved