You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Li Lu (JIRA)" <ji...@apache.org> on 2015/10/02 00:44:26 UTC

[jira] [Commented] (YARN-4220) [Storage implementation] Support getEntities with only Application id but no flow and flow run ID

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

Li Lu commented on YARN-4220:
-----------------------------

Well, seems like flow and flowrun ids can be easily cached on the client side. Reduce the priority of this. 

> [Storage implementation] Support getEntities with only Application id but no flow and flow run ID
> -------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4220
>                 URL: https://issues.apache.org/jira/browse/YARN-4220
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Li Lu
>            Assignee: Li Lu
>            Priority: Minor
>
> Currently we're enforcing flow and flowrun id to be non-null values on {{getEntities}}. We can actually query the appToFlow table to figure out an application's flow id and flowrun id if they're missing. This will simplify normal queries. 



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