hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8877) Rename o.a.h.security.token.Token.TrivialRenewer to UnmanagedRenewer for clarity
Date Thu, 11 Oct 2012 20:45:03 GMT

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

Karthik Kambatla updated HADOOP-8877:

    Resolution: Won't Fix
        Status: Resolved  (was: Patch Available)

Trivial change, closing as won't fix for now. Can re-open and commit changes later if need
> Rename o.a.h.security.token.Token.TrivialRenewer to UnmanagedRenewer for clarity
> --------------------------------------------------------------------------------
>                 Key: HADOOP-8877
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8877
>             Project: Hadoop Common
>          Issue Type: Wish
>    Affects Versions: 2.0.1-alpha
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>            Priority: Trivial
>         Attachments: hadoop-8877.patch
> While browsing through the code, I came across the TrivialRenewer. It would definitely
be easy to comprehend if we rename it to UnmanagedRenewer.

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

View raw message