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:44:45 GMT

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

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

Storing metric values(which are numbers) as string is fine if we want to check them for equality.
But we have to support all relational operations for metrics. And that is where string representation
doesnt work.
This is because in HBase, filters currently use lexicographical comparison. This means that
with current mechanism to store metric values, a value of 4000 will be judged as smaller than
60.


> 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