[ 
https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohith Sharma K S updated YARN-6027:
------------------------------------
    Attachment: YARN-6027-YARN-5355.0001.patch

Attaching the patch for improving /flows API with following changes. Patch adds 
3 new filter i.e *fromid* *userid* and *collapse*. 
# As discussed previously, the new filter to collapse has been provided. It 
basically collapses for the user-flowName across the days. 
# *fromId* filter has been added which support in either of the mode i.e 
without collapsing and with collapsing. 
# *userid* filter is added to retrieve per user flows. It can be used 
congestion with any other filter such as fromid, userid, daterange and 
collapse. 

cc :-/ [~varun_saxena] [~sjlee0] [~vrushalic] [~gtCarrera9] request to review 
the patch. 

> 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]

Reply via email to