big-data/hadoop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

HADOOP-16710. Testing_azure.md documentation is misleading.

Browse Source 
Contributed by Andras Bokor.

Change-Id: Icf07a53145936953629c7dace2e9648b7b21588d
This commit is contained in:
Andras Bokor 2019-11-17 17:04:29 +00:00 committed by Steve Loughran
parent b3119b9ab6
commit 96c4520f89
No known key found for this signature in database
GPG Key ID: D22CF846DBB162A0
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
hadoop-tools/hadoop-azure/src/site/markdown/testing_azure.md
View File

@ -153,13 +153,18 @@ mvn -T 1C clean verify
```
It's also possible to execute multiple test suites in parallel by passing the
`parallel-tests` property on the command line. The tests spend most of their
`parallel-tests=wasb|abfs|both` property on the command line. The tests spend most of their
time blocked on network I/O, so running in parallel tends to
complete full test runs faster.
```bash
mvn -T 1C -Dparallel-tests clean verify
mvn -T 1C -Dparallel-tests=both clean verify
mvn -T 1C -Dparallel-tests=wasb clean verify
mvn -T 1C -Dparallel-tests=abfs clean verify
```
`-Dparallel-tests=wasb` runs the WASB related integration tests from azure directory<br/>
`-Dparallel-tests=abfs` runs the ABFS related integration tests from azurebfs directory<br/>
`-Dparallel-tests=both` runs all the integration tests from both azure and azurebfs directory<br/>
Some tests must run with exclusive access to the storage container, so even with the
`parallel-tests` property, several test suites will run in serial in a separate