You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "Thomas Weise (JIRA)" <ji...@apache.org> on 2015/12/28 01:25:49 UTC

[jira] [Closed] (APEXCORE-71) Support different names for namenode and yarn delegation token max lifetime settings

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

Thomas Weise closed APEXCORE-71.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 3.2.0

> Support different names for namenode and yarn delegation token max lifetime settings
> ------------------------------------------------------------------------------------
>
>                 Key: APEXCORE-71
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-71
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: gaurav gupta
>            Assignee: gaurav gupta
>             Fix For: 3.2.0
>
>
> Currently we use hadoop property names for yarn and namenode delegation tokens when they need to be specified in our configs as well. This will lead to incorrect handling through the web service calls. Can we enhance this behavior to use our own property names for these settings and if these are not available then use the hadoop property names.



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