Vrushali C commented on YARN-4074:

bq. Should we support filtering on the basis of flow start time and probably 
end time as well ?

Going forward, yes, we do need to have a timerange parameter for queries. But 
for the PoC we work with what is being fetched/returned.

bq. Moreover, do we return metrics at all times for a flow run ? Or make 
returning on metric field conditional ? Just confirming because then I would 
not need fields as a query parameter in REST.

For the PoC we can return everything that is being fetched/ whatever is easier. 
But as such, we do need filtering out of metrics and returning subsets of 
metrics etc, so these query parameters would need to be worked out. We have to 
think about how we can allow for filtering of metrics, but we would anyways 
need a basic API that returns everything for a flow run, so I think for more 
enhancements can be added in later after the PoC, what do you think? 

> [timeline reader] implement support for querying for flows and flow runs
> ------------------------------------------------------------------------
>                 Key: YARN-4074
>                 URL: https://issues.apache.org/jira/browse/YARN-4074
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>         Attachments: YARN-4074-YARN-2928.POC.001.patch, 
> YARN-4074-YARN-2928.POC.002.patch
> Implement support for querying for flows and flow runs.
> We should be able to query for the most recent N flows, etc.
> This includes changes to the {{TimelineReader}} API if necessary, as well as 
> implementation of the API.

This message was sent by Atlassian JIRA

Reply via email to