[
https://issues.apache.org/jira/browse/HADOOP-12563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105754#comment-15105754
]
Allen Wittenauer commented on HADOOP-12563:
-------------------------------------------
bq. can we talk about the ability to have different formats now or do we have
to talk about adding the ability in a follow up to this?
I'd prefer we cover them as a separate JIRA. My plan was to only commit this
to trunk, since we already know that some ecosystem projects (e.g., Spark) are
doing question stuff like shading the Credential class. If everyone thinks the
general framework here is OK, then let's commit this and spread out/move on to
further enhancements such as adding other token formats.
(Yes, technically the changes here are "legally" compatible. But there have
been enough surprising/damaging changes in branch-2 throughout it's extremely
long lifetime that unless one completely disregards the users, it's
unconscionable to make the situation even worse by committing this there.)
> Updated utility to create/modify token files
> --------------------------------------------
>
> Key: HADOOP-12563
> URL: https://issues.apache.org/jira/browse/HADOOP-12563
> Project: Hadoop Common
> Issue Type: New Feature
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Assignee: Matthew Paduano
> Attachments: HADOOP-12563.01.patch, HADOOP-12563.02.patch,
> HADOOP-12563.03.patch, HADOOP-12563.04.patch, HADOOP-12563.05.patch,
> HADOOP-12563.06.patch, example_dtutil_commands_and_output.txt,
> generalized_token_case.pdf
>
>
> hdfs fetchdt is missing some critical features and is geared almost
> exclusively towards HDFS operations. Additionally, the token files that are
> created use Java serializations which are hard/impossible to deal with in
> other languages. It should be replaced with a better utility in common that
> can read/write protobuf-based token files, has enough flexibility to be used
> with other services, and offers key functionality such as append and rename.
> The old version file format should still be supported for backward
> compatibility, but will be effectively deprecated.
> A follow-on JIRA will deprecrate fetchdt.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
