[
https://issues.apache.org/jira/browse/HDFS-13617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979566#comment-16979566
]
Chen Liang commented on HDFS-13617:
-----------------------------------
Thanks for taking a look [~ste...@apache.org] and the suggestions! Sure,
totally makes sense to me. It was just that the uber Jira was intended to be
just a HDFS feature, so I put it under HDFS, and when creating sub-tasks, it
just automatically got created as HDFS issues too. Probably should have filed
those separately.
Moving forward, will definitely take this into account in the future. But given
that this particular Jira has been committed, do you prefer we still change the
corresponding Jiras to HADOOP project?
> Allow wrapping NN QOP into token in encrypted message
> -----------------------------------------------------
>
> Key: HDFS-13617
> URL: https://issues.apache.org/jira/browse/HDFS-13617
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Chen Liang
> Assignee: Chen Liang
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: HDFS-13617.001.patch, HDFS-13617.002.patch,
> HDFS-13617.003.patch, HDFS-13617.004.patch, HDFS-13617.005.patch,
> HDFS-13617.006.patch, HDFS-13617.007.patch, HDFS-13617.008.patch,
> HDFS-13617.009.patch
>
>
> This Jira allows NN to configurably wrap the QOP it has established with the
> client into the token message sent back to the client. The QOP is sent back
> in encrypted message, using BlockAccessToken encryption key as the key.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
