[
https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859028#comment-15859028
]
Rohith Sharma K S commented on YARN-6027:
-----------------------------------------
[~gtCarrera9]
Currently, flow activities are tracked by daily basis. When user retrieves
flows using just */flows* , it returns flow entities for the user-flowname as
different entities. It is useful when flow activities to be tracked by daily
basis.
But more generally, user wants to track flows as single entity. User need his
flows given time range. In such cases, entities retrieved can not be duplicate
for user-flowname. The segregation of all the flows for the combination
user-flowname should be done at reader end. Default behavior is kept as-is with
existing API and introducing more filters to /flows.
Filter user/fromid will work without collapse mode also. All filters works
independently and with combine also. I do not fully agree it is group by
operation if you are pointing out from sql background. API still maintains the
order of execution time.
> Improve /flows API for more flexible filters fromid, collapse, userid
> ---------------------------------------------------------------------
>
> Key: YARN-6027
> URL: https://issues.apache.org/jira/browse/YARN-6027
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Labels: yarn-5355-merge-blocker
> Attachments: YARN-6027-YARN-5355.0001.patch
>
>
> In YARN-5585 , fromId is supported for retrieving entities. We need similar
> filter for flows/flowRun apps and flow run and flow as well.
> Along with supporting fromId, this JIRA should also discuss following points
> * Should we throw an exception for entities/entity retrieval if duplicates
> found?
> * TimelieEntity :
> ** Should equals method also check for idPrefix?
> ** Does idPrefix is part of identifiers?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
