[
https://issues.apache.org/jira/browse/HDFS-6490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066526#comment-14066526
]
Charles Lamb commented on HDFS-6490:
------------------------------------
bq. In non federated cluster configurations, this will return null right. So,
in that case, plan is to just skip including nameserviceID?
Correct.
bq. From the description, we need to create the key in the format of host:port.
But seems like we are trying that only for ketVersion now and id is considering
as still randomUUID?
Yes, sorry, the description is old. We decided to give up on HOST:PORT and just
use nameserviceID if it is available.
The idea is to try to get something more descriptive than the UUID in the key
description.
> Fix the keyid format for generated keys in FSNamesystem.createEncryptionZone
> -----------------------------------------------------------------------------
>
> Key: HDFS-6490
> URL: https://issues.apache.org/jira/browse/HDFS-6490
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode, security
> Affects Versions: fs-encryption (HADOOP-10150 and HDFS-6134)
> Reporter: Charles Lamb
> Assignee: Charles Lamb
> Attachments: HDFS-6490.001.patch, HDFS-6490.002.patch
>
>
> FSNamesystem.createEncryptionZone needs to create key ids with the format
> hdfs://HOST:PORT/<pathOfEZ>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
