Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 6 Oct 2015 18:05:27 +0000 (UTC)
From: "Varun Saxena (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12875438.1442515505000.38280.1444154727572@Atlassian.JIRA>
In-Reply-To: <JIRA.12875438.1442515505000@Atlassian.JIRA>
References: <JIRA.12875438.1442515505000@Atlassian.JIRA>
 <JIRA.12875438.1442515505273@arcas>
Subject: [jira] [Commented] (YARN-4178) [storage implementation] app id as
 string in row keys can cause incorrect ordering
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Varun Saxena commented on YARN-4178:
------------------------------------

Ok. But then should we rename the other one as invertLong ?

> [storage implementation] app id as string in row keys can cause incorrect ordering
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-4178
>                 URL: https://issues.apache.org/jira/browse/YARN-4178
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Sangjin Lee
>            Assignee: Varun Saxena
>         Attachments: YARN-4178-YARN-2928.01.patch, YARN-4178-YARN-2928.02.patch, YARN-4178-YARN-2928.03.patch, YARN-4178-YARN-2928.04.patch
>
>
> Currently the app id is used in various places as part of row keys. However, currently they are treated as strings. This will cause a problem with ordering when the id portion of the app id rolls over to the next digit.
> For example, "app_1234567890_10000" will be considered *earlier* than "app_1234567890_9999". We should correct this.


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