hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5379) Include FS delegation token ID in job conf
Date Tue, 16 Jul 2013 23:18:50 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710445#comment-13710445
] 

Daryn Sharp commented on MAPREDUCE-5379:
----------------------------------------

Yes, the whole identifier must considered opaque.  Anything that requires the client to decode
a token is a non-starter because of all the future incompatibilities it will cause.  I myself
would love traceability but this isn't the way to do it.
                
> Include FS delegation token ID in job conf
> ------------------------------------------
>
>                 Key: MAPREDUCE-5379
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5379
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: job submission, security
>    Affects Versions: 2.1.0-beta
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>         Attachments: MAPREDUCE-5379-1.patch, MAPREDUCE-5379.patch
>
>
> Making a job's FS delegation token ID accessible will allow external services to associate
it with the file system operations it performs.

--
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

Mime
View raw message