[
https://issues.apache.org/jira/browse/HDFS-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605628#comment-13605628
]
Scott Forman commented on HDFS-3627:
------------------------------------
My initial patch (30/Jan/13) did not modify the DelegationKey class. It had,
as you suggested, the tool create the base64 representation of the encoded key.
But that solution made it very difficult to create a unit test, so that is what
motivated me to modify the DelegationKey class to show that an equivalent
DelegationKey could be constructed from the fields output by the offline tool.
I agree that it would be better to have the patch only touch the classes in the
offline tool. Could we use the initial patch, which does not provide a unit
test?
> OfflineImageViewer oiv Indented processor prints out the Java class name in
> the DELEGATION_KEY field
> ----------------------------------------------------------------------------------------------------
>
> Key: HDFS-3627
> URL: https://issues.apache.org/jira/browse/HDFS-3627
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Ravi Prakash
> Priority: Minor
> Attachments: HDFS-3627.patch, HDFS-3627.patch, HDFS-3627.patch,
> HDFS-3627.patch
>
>
> Instead of the contents of the delegation key this is printed out
> DELEGATION_KEY =
> org.apache.hadoop.security.token.delegation.DelegationKey@1e2ca7
> DELEGATION_KEY =
> org.apache.hadoop.security.token.delegation.DelegationKey@105bd58
> DELEGATION_KEY =
> org.apache.hadoop.security.token.delegation.DelegationKey@1d1e730
> DELEGATION_KEY =
> org.apache.hadoop.security.token.delegation.DelegationKey@1a116c9
> DELEGATION_KEY =
> org.apache.hadoop.security.token.delegation.DelegationKey@df1832
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
