Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2757AF996 for ; Tue, 2 Apr 2013 19:27:18 +0000 (UTC) Received: (qmail 46913 invoked by uid 500); 2 Apr 2013 19:27:18 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 46876 invoked by uid 500); 2 Apr 2013 19:27:18 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 46867 invoked by uid 99); 2 Apr 2013 19:27:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Apr 2013 19:27:18 +0000 Date: Tue, 2 Apr 2013 19:27:17 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (YARN-442) The ID classes should be immutable MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-442. ------------------------------------------ Resolution: Duplicate Assignee: (was: Xuan Gong) YARN-528 is fixing this, closing as duplicate. > The ID classes should be immutable > ---------------------------------- > > Key: YARN-442 > URL: https://issues.apache.org/jira/browse/YARN-442 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Siddharth Seth > > ApplicationId, ApplicationAttemptId, ContainerId should be immutable. That should allow for a simpler implementation as well as remove synchronization. -- 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