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-4053) Change the way metric values are stored in HBase Storage
Date Fri, 14 Aug 2015 17:47:46 GMT

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

Varun Saxena commented on YARN-4053:
------------------------------------

Also for floating point metrics, query can be in integral form. This can create issues too.
We should clearly document that query should also be in decimal representation for such metrics.
That is, checking for condition like m1 > 40 should be mean query from client should have
filter as {{m1 > 40.0}} in REST API. So that its interpreted as a floating point number

> Change the way metric values are stored in HBase Storage
> --------------------------------------------------------
>
>                 Key: YARN-4053
>                 URL: https://issues.apache.org/jira/browse/YARN-4053
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>
> Currently HBase implementation uses GenericObjectMapper is used to convert and store
values in backend HBase storage. This converts everything into a string representation(ASCII/UTF-8
encoded byte array).
> While this is fine in most cases, it does not quite serve our use case for metrics. 
> So we need to decide how are we going to encode and decode metric values and store them
in HBase.
>  



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

Mime
View raw message