[jira] [Commented] (YARN-3862) Support for fetching specific configs and metrics based on prefixes

["Varun Saxena (JIRA)" <ji...@apache.org>]

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

Varun Saxena commented on YARN-3862:
------------------------------------

[~sjlee0]
Looking at the code again, I am actually using getColumnPrefixBytes in FlowRunEntityReader and passing it to TimelineFilterUtils. However in ApplicationEntityReader and GenericEntityReader I am assuming columnprefix is null so haven't used it, which I agree is wrong.

However I have exposed a method as under. Here colPrefix is meant to take column prefix bytes as argument.
{{public static FilterList createHBaseFilterList(byte[] colPrefix, TimelineFilterList filterList)}}
I think this should be enough. However user can then pass any sequence of bytes as prefix. But it wont be as if current code will break due to change in the way column prefixes are encoded if the caller of this code is correct.

Another alternative would be to pass ColumnPrefix object to TimelineFilterUtils and call getColumnPrefixBytes from there.
Thoughts ?

> Support for fetching specific configs and metrics based on prefixes
> -------------------------------------------------------------------
>
>                 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
>              Labels: yarn-2928-1st-milestone
>         Attachments: YARN-3862-YARN-2928.wip.01.patch, YARN-3862-YARN-2928.wip.02.patch, YARN-3862-feature-YARN-2928.wip.03.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
(v6.3.4#6332)