HDFS-11175. Document uppercase key names are not supported in 
TransparentEncryption.md. Contributed by Yiqun Lin.


Project: http://git-wip-us.apache.org/repos/asf/hadoop/repo
Commit: http://git-wip-us.apache.org/repos/asf/hadoop/commit/636f7547
Tree: http://git-wip-us.apache.org/repos/asf/hadoop/tree/636f7547
Diff: http://git-wip-us.apache.org/repos/asf/hadoop/diff/636f7547

Branch: refs/heads/HADOOP-13345
Commit: 636f7547b7067c315cf5448d77e49a8fe55651b3
Parents: 01665e4
Author: Akira Ajisaka <[email protected]>
Authored: Fri Nov 25 17:48:54 2016 +0900
Committer: Akira Ajisaka <[email protected]>
Committed: Fri Nov 25 17:48:54 2016 +0900

----------------------------------------------------------------------
 .../hadoop-hdfs/src/site/markdown/TransparentEncryption.md         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hadoop/blob/636f7547/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/TransparentEncryption.md
----------------------------------------------------------------------
diff --git 
a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/TransparentEncryption.md 
b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/TransparentEncryption.md
index b82b400..1a403c6 100644
--- a/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/TransparentEncryption.md
+++ b/hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/TransparentEncryption.md
@@ -173,7 +173,7 @@ Create a new encryption zone.
 | | |
 |:---- |:---- |
 | *path* | The path of the encryption zone to create. It must be an empty 
directory. A trash directory is provisioned under this path.|
-| *keyName* | Name of the key to use for the encryption zone. |
+| *keyName* | Name of the key to use for the encryption zone. Uppercase key 
names are unsupported. |
 
 ### <a name="listZones"></a>listZones
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to