[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933544#comment-14933544 ] Hadoop QA commented on YARN-4178: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933487#comment-14933487 ] Varun Saxena commented on YARN-4178: After giving some further thought over it, in the patch, I have

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933506#comment-14933506 ] Varun Saxena commented on YARN-4178: Also for the sake of consistency, I have done the conversion

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14901057#comment-14901057 ] Varun Saxena commented on YARN-4178: [~jrottinghuis], No, I did not mean that we can use

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14900927#comment-14900927 ] Joep Rottinghuis commented on YARN-4178: [~varun_saxena] if you mean

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877046#comment-14877046 ] Varun Saxena commented on YARN-4178: bq. we certainly have to store the application_ part. I think we

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877044#comment-14877044 ] Varun Saxena commented on YARN-4178: As appId is part of entity table row key, on second thoughts,

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804423#comment-14804423 ] Vrushali C commented on YARN-4178: -- In hRaven, we started with storing hadoop job ids as a tuple of JT/RM

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1480#comment-1480 ] Li Lu commented on YARN-4178: - We can rely on ApplicationId class in YARN api to fix this, right? As

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804414#comment-14804414 ] Varun Saxena commented on YARN-4178: ApplicationId is basically a combination of cluster timestamp and

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804487#comment-14804487 ] Joep Rottinghuis commented on YARN-4178: [~vrushalic] we certainly have to store the application_