Steve Loughran

with #6789 in, there's space in fs.s3a.performance.flags for this. I think I even created the enum option for you...

merged to trunk, cherrypicked to branch 3.4, reran modified test. if you want branch-3.3.x support, do a test run yourself and push up a new pr

moved to hadoop; azure component. now, the bad news: as it goes near a cloud store, you *have* to run the entire hadoop-azure tests for the wasb component, and tell...

@xuzifu666 yes. 1. Which azure region did you run all the wasb tests against 2. and what were your maven command line arguments used? 3. did any tests fail?

let me try and test this myself.

(which I can't do today as both my hadoop source trees are testing my "support parallel tests against the same s3 bucket" right now...

I've been away for a week and am catching up, so not tested yet, sorry...

@xuzifu666 before I merge, what name do you want to be credited with in the patch...your github account doesn't have one.

thanks, merged to trunk and updated the JIRA. If you do a cherrypick of this commit and submit as a PR against branch-3.4 I'll merge it there too, once yetus...

based on #4298