Sangjin Lee commented on YARN-3051:

Wanted to add my 2 cents before the weekend.

As for the default view of an entity, are we agreed then that it means all the 
data at the level of the entity but *not* going into config/metrics/info? I 
want to stress that this default behavior should be explicit in the code so 
there is no confusion.

I think it's up to us to define in terms of APIs how to best capture all the 
query use cases. If it can be worked through fieldsToRetrieve, that is fine. We 
need to make sure the APIs are clear in terms of what they do.

The following are the types of queries that I can think of this storage reader 
API (and the reader itself) would need to support. This is not an exhaustive 
list. There may be more. But at least these need to be supported well:
- given an id, return the entity (default; see above)
- given an id, return all metrics of the entity
- given an id, return the entire config of the entity
- given an id, return the entity along with metrics/configs/info
- (optional?) given an id, return one metric or some metrics (by name) of the 
entity (possibly retrieving the time series of its values)
- (optional?) given an id, return one of some config entries (by name) of the 
- (need to give some more thoughts) relational queries (e.g. given an app id, 
return the app entity along with its containers)

Again, this is not an exhaustive list, or even a completely thought-out list. 
But it should give us some idea on how to define the APIs. Hope this helps...

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