[
https://issues.apache.org/jira/browse/HADOOP-12563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085909#comment-15085909
]
Allen Wittenauer commented on HADOOP-12563:
-------------------------------------------
bq. I'm also curious about the choice of protobuf for the token rather than
JWT. I'd like to understand the differences in portability that you see between
the two. JWT has become a very popular format for such things.
* extremely portable; hooks for almost every language you can think of
* if the app is doing RPC (probably the majority case today for most DT file
usage), protobuf libraries are already available
* changing from one serialization format to another is a fairly trivial change;
the content is left mostly untouched so avoid the conversation of what goes
where
* can be evolved to support more fields (e.g., service aliasing, something
we've been discussing internally) as necessary
The ability to support more than one format is part of the design here. If
protobuf isn't sufficient to handle all uses cases another format could be
added easily enough. e.g., there's no reason why JWT couldn't be added as a
third option at a later date.
> 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)
