hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11825) Move timelineclient Jersey+Kerberos+UGI support into a public implementation
Date Sun, 12 Apr 2015 20:50:12 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-11825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491713#comment-14491713

Steve Loughran commented on HADOOP-11825:

yes, it was one, along with WebHDFS. Did you write the KMS one? If so, was it a cut-and-paste?

> Move timelineclient Jersey+Kerberos+UGI support into a public implementation
> ----------------------------------------------------------------------------
>                 Key: HADOOP-11825
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11825
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: net
>    Affects Versions: 2.7.0
>            Reporter: Steve Loughran
>   Original Estimate: 4h
>  Remaining Estimate: 4h
> Having a SPNEGO authed Jersey REST client is a pre-requisite for REST operations against
YARN applications and any other services in the Hadoop cluster which use Kerberos to auth,
from code that uses UGI to manage identity.
> There's a multiple implementations of UGI+Http bindings in the code, with {{org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl}}
 being the one which provides Jersey client integration, and:
> # retry
> # delegation tokens
> # {{doAs()}} support
> It does all of this intermixed with the rest of the code, and is tagged as private.
> I propose pulling the jersey support out into a hadoop common .net class, tagging as
public+evolving, to act as the foundation for any app that needs to use UGI+SPNEGO with jersey

This message was sent by Atlassian JIRA

View raw message