Sangjin Lee commented on YARN-3051:

I agree we need to support all these queries, but we don't need to make 
different REST API endpoint for each. We can always use the getEntity API, but 
use different query params, including the field-to-retrieve and the 
metrics/configs filter. Entity wrapper with the minimal view shouldn't result 
in much overhead, and the response is much self-container, such that you can 
know which entity one config/metric is related to without going back to check 
the request.

Sure. My point was that the APIs need to support all these queries well. It 
wasn't about having a separate REST API endpoint (or separate method) for each 
of these types. If we have a base REST API and the java API that support all 
these well, all the better.

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