hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3862) Decide which contents to retrieve and send back in response in TimelineReader
Date Fri, 14 Aug 2015 20:07:47 GMT

    [ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697663#comment-14697663

Varun Saxena commented on YARN-3862:

bq. My feeling is that the concept of timeline filter may become a part of our object model,
so that client users can easily communicate?
Do we want to expose it to the client ? Suggestion sounds good. That wasnt the plan but if
everyone agrees, lets have it that way.

bq. are we treating our timeline filters as pure-data objects (models) 
Yes I am as of now treating them as pure data objects. That is why instead of using polymorphism
and converting the filter to HBase Filter by providing a method for conversion in the filter
class(es), I kept the conversion in util class. The intention was to decouple filters from
storage implementation.

bq. is it easy, or possible, for us to implement a "paging filter"? 
Will look into it.

> Decide which contents to retrieve and send back in response in TimelineReader
> -----------------------------------------------------------------------------
>                 Key: YARN-3862
>                 URL: https://issues.apache.org/jira/browse/YARN-3862
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>         Attachments: YARN-3862-YARN-2928.wip.01.patch
> Currently, we will retrieve all the contents of the field if that field is specified
in the query API. In case of configs and metrics, this can become a lot of data even though
the user doesn't need it. So we need to provide a way to query only a set of configs or metrics.
> As a comma spearated list of configs/metrics to be returned will be quite cumbersome
to specify, we have to support either of the following options :
> # Prefix match
> # Regex
> # Group the configs/metrics and query that group.
> We also need a facility to specify a metric time window to return metrics in a that window.
This may be useful in plotting graphs 

This message was sent by Atlassian JIRA

View raw message