[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sangjin Lee updated YARN-4178: ------------------------------ Description: 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. was: Currently the app id is used in various places as part of row keys and in column names. However, they are treated as strings for the most part. 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_100" will be considered *earlier* than "app_1234567890_99". We should correct this. > [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 > > > 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)