Varun Saxena commented on YARN-4178:

bq. As for the "application" prefix, is there a discussion in the YARN 
community in general of making this prefix customizable? I'm just not familiar 
with the current state of that discussion, although I recall hearing about it 
in the past. That would help us determine whether this is significant enough 
for us to care about it.
I haven't come across any such active discussion recently. [~vinodkv] might be 
knowing whether there is any such pre-decided future plan as well. 
Even if a prefix is added in future we would most probably encapsulate that 
inside ApplicationId class itself i.e. prefix will be a an additional field 
instead of a static string(application_). So while checking for references of 
this class, person changing or reviewing the code would come across this code 
as well and should take necessary action i.e. storing the prefix in HBase, IMO. 
Thoughts ?

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

Reply via email to