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 "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2016/08/30 05:01:20 UTC
[jira] [Commented] (YARN-4220) [Storage implementation] Support
getEntities with only Application id but no userId
[ https://issues.apache.org/jira/browse/YARN-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448041#comment-15448041 ]
Rohith Sharma K S commented on YARN-4220:
-----------------------------------------
Multiple application entity reader enforces to provide userId and flowName as a filter. It looks like userId and flowName are tightly coupled for multiple applications retrieval.
> [Storage implementation] Support getEntities with only Application id but no userId
> -----------------------------------------------------------------------------------
>
> 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
> Labels: YARN-5355
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org