You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-commits@hadoop.apache.org by li...@apache.org on 2019/12/11 19:56:28 UTC

[hadoop] branch branch-3.0 updated: HADOOP-16758. Refine testing.md to tell user better how to use auth-keys.xml (#1753)

This is an automated email from the ASF dual-hosted git repository.

liuml07 pushed a commit to branch branch-3.0
in repository https://gitbox.apache.org/repos/asf/hadoop.git


The following commit(s) were added to refs/heads/branch-3.0 by this push:
     new 109a2f5  HADOOP-16758. Refine testing.md to tell user better how to use auth-keys.xml (#1753)
109a2f5 is described below

commit 109a2f513f1c889c325a454575aafe3cba1f5f25
Author: Mingliang Liu <li...@apache.org>
AuthorDate: Wed Dec 11 11:52:53 2019 -0800

    HADOOP-16758. Refine testing.md to tell user better how to use auth-keys.xml (#1753)
    
    Contributed by Mingliang Liu
---
 .../hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md       | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md b/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
index cf7a2e4..836bc1f 100644
--- a/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
+++ b/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
@@ -151,8 +151,9 @@ Example:
 
 For S3a encryption tests to run correctly, the
 `fs.s3a.server-side-encryption.key` must be configured in the s3a contract xml
-file with a AWS KMS encryption key arn as this value is different for each AWS
-KMS.
+file or `auth-keys.xml` file with a AWS KMS encryption key arn as this value is
+different for each AWS KMS. Please note this KMS key should be created in the
+same region as your S3 bucket. Otherwise, you may get `KMS.NotFoundException`.
 
 Example:
 
@@ -903,7 +904,7 @@ mvn -T 1C verify -Dtest=skip -Dit.test=ITestS3AMiscOperations -Ds3guard -Ddynamo
 ### Notes
 
 1. If the `s3guard` profile is not set, then the S3Guard properties are those
-of the test configuration set in `contract-test-options.xml` or `auth-keys.xml`
+of the test configuration set in s3a contract xml file or `auth-keys.xml`
 
 If the `s3guard` profile *is* set,
 1. The S3Guard options from maven (the dynamo and authoritative flags)


---------------------------------------------------------------------
To unsubscribe, e-mail: common-commits-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-commits-help@hadoop.apache.org