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

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

[~gtCarrera9], these 2 JIRAs' were raised separately to address following areas 
:
# Enhance already supported filters (YARN-3863) to filter out rows of data. By 
adding support for OR in addition to AND and relational ops for metrics.  Scope 
for this JIRA is pretty clear.
# Restrict the amount of data retrieved(from columns) in this JIRA. In this 
JIRA, we actually wanted to have a discussion on what all we need to support. 
Regex, prefix match , etc. Also whether we want to retrieve metrics by time 
windows as well.

I am open to realigning these JIRAs' and distributing the work along the lines 
of the workflow you mentioned above.
My only concern with deciding with a filter object model though will be that we 
may take a lot of time deciding it to cover all the scenarios. Because support 
for additional filters may come up during further discussion. 
Let's do as per whatever is the consensus.

> 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
(v6.3.4#6332)

Reply via email to