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

Posted to yarn-issues@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2013/05/22 06:33:21 UTC

[jira] [Commented] (YARN-716) Make ApplicationID immutable

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

Alejandro Abdelnur commented on YARN-716:
-----------------------------------------

I wonder if it is not worth doing what [~revans2] suggested in today's ser/deser email thread regarding exposing directly PROTO classes. Doing so it would take care automatically -due to the nature of the PB classes- of quite a JIRAs in progress: YARN-716, YARN-710, YARN-711, YARN-528, and others. It would also get rid of significant amount of repetitive/error-prone code that translates from PROTO to PBImpl and viceversa. Maybe, what I've joked about sending everybody on vacations for while, locking down commits for a couple of days, while doing this would work. Thoughts?
                
> Make ApplicationID immutable
> ----------------------------
>
>                 Key: YARN-716
>                 URL: https://issues.apache.org/jira/browse/YARN-716
>             Project: Hadoop YARN
>          Issue Type: Task
>    Affects Versions: 2.0.4-alpha
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: YARN-716.txt
>
>


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