You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Vrushali C (JIRA)" <ji...@apache.org> on 2016/04/21 21:21:26 UTC

[jira] [Assigned] (YARN-4786) Enhance hbase coprocessor aggregation operations:GLOBAL_MIN, LATEST_MIN etc and FINAL attributes

     [ https://issues.apache.org/jira/browse/YARN-4786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vrushali C reassigned YARN-4786:
--------------------------------

    Assignee: Vrushali C

> Enhance hbase coprocessor aggregation operations:GLOBAL_MIN, LATEST_MIN etc and FINAL attributes
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4786
>                 URL: https://issues.apache.org/jira/browse/YARN-4786
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Vrushali C
>            Assignee: Vrushali C
>
> As part of YARN-4062, Joep and I had been discussing about min, max operations and the final attributes. 
> YARN-4062 has GLOBAL_MIN, GLOBAL_MAX and SUM operations. It presently indicates SUM_FINAL for a cell that contains a metric that is the final value for the metric.
> We should enhance this such that the set of aggregation dimensions SUM, MIN, MAX, etc. are really set of a per-column level and shouldn't be passed from the client, but be instrumented by the ColumnHelper infrastructure instead. We should probably use a different tag value for that.
> Both aggregation dimension and this "FINAL_VALUE" or whatever abbreviation we use are needed to determine the right thing to do for compaction. Only one value needs to have this final value bit / tag set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)