Sangjin Lee commented on YARN-3051:

A couple of things to discuss:

In principle, a *shallow* view of the entity will be returned by default, 
right? Specifically, I'm wondering whether all configs and metrics should be 
included in the default view or not. I wonder what ATS v.1 does in this regard? 
FYI, I believe most of the YARN REST API returns a shall view of objects. Note 
that the size of the responses could become quite big if we include configs and 
metrics by default.

On a related note, if we decide to return shallow views by default, then the 
question is, how do we ask the reader to get things like configs and metrics? 
The reader API as well as the reader storage interface should be able to 
support calls to retrieve config/metrics, perhaps with new methods.

bq. For instance, queries such as get apps which have a particular metric's 
value less than or greater than something ?

Metric/config-based queries will probably need changes to the API. We would 
want to be able to queries like "return apps where config X = Y" or "return 
apps where metric A > B". But we can consider them advanced queries.

> [Storage abstraction] Create backing storage read interface for ATS readers
> ---------------------------------------------------------------------------
>                 Key: YARN-3051
>                 URL: https://issues.apache.org/jira/browse/YARN-3051
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Varun Saxena
> Per design in YARN-2928, create backing storage read interface that can be 
> implemented by multiple backing storage implementations.

This message was sent by Atlassian JIRA

Reply via email to