[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=15586087#comment-15586087
]
Sangjin Lee commented on YARN-4220:
---
+1.
> [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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[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=15583852#comment-15583852
]
Li Lu commented on YARN-4220:
-
After we finished UI integration and streamlined most UI use cases in
YARN-5561, I believe this JIRA can be closed? Is there a special need to
support the use case proposed in this JIRA?
> [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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[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=15450357#comment-15450357
]
Li Lu commented on YARN-4220:
-
Folks sorry for the delay... I think I may need some time to catch up with my
own proposed fix, but if a fix is already in someone's mind, please feel free
to reassign the JIRA. I can help with reviewing if needed. Thanks!
> [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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[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=15448154#comment-15448154
]
Varun Saxena commented on YARN-4220:
We can simply skip retrieving flow, flowrun, app entities if a call comes via
getEntities endpoint.
> [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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
