reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anupam (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (REEF-875) Handle Hadoop security tokens in .NET client
Date Fri, 25 Mar 2016 05:03:25 GMT

     [ https://issues.apache.org/jira/browse/REEF-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anupam updated REEF-875:
------------------------
    Description: 
(This issue is specific to REEF over YARN.)
REEF Java client provides ability for user to setup Hadoop security tokens since the completion
of [REEF-604].
Legacy REEF .NET client which assembled parameters and called into Java client for REEF application
could use this support to provide Hadoop security token [REEF-782]. After the implementation
of native REEF .NET client [REEF-1019] which uses YARN REST APIs we need to provide Hadoop
security token support in the new client to achieve feature parity with legacy .NET client
so that it can be deprecated.

> Handle Hadoop security tokens in .NET client
> --------------------------------------------
>
>                 Key: REEF-875
>                 URL: https://issues.apache.org/jira/browse/REEF-875
>             Project: REEF
>          Issue Type: New Feature
>            Reporter: Anupam
>
> (This issue is specific to REEF over YARN.)
> REEF Java client provides ability for user to setup Hadoop security tokens since the
completion of [REEF-604].
> Legacy REEF .NET client which assembled parameters and called into Java client for REEF
application could use this support to provide Hadoop security token [REEF-782]. After the
implementation of native REEF .NET client [REEF-1019] which uses YARN REST APIs we need to
provide Hadoop security token support in the new client to achieve feature parity with legacy
.NET client so that it can be deprecated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message