Zhijie Shen commented on YARN-3411:

[~vrushalic], I've commented on 
 about the question of config/info/metric value.

I scan through the hbase implementation. It seem config value is treated as 
string, info is stored as directly in bytes, and metrics is treated as Long. I 
kindly agree on config/info, and I think it should be fine if config is assumed 
to be string (maybe we need to adjust the data model), but let's see 
community's opinion. For metrics, shall we be more generalized to support all 
kinds of numeric value, boolean and so on?

> [Storage implementation] explore the native HBase write schema for storage
> --------------------------------------------------------------------------
>                 Key: YARN-3411
>                 URL: https://issues.apache.org/jira/browse/YARN-3411
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Vrushali C
>            Priority: Critical
>         Attachments: ATSv2BackendHBaseSchemaproposal.pdf, 
> YARN-3411.poc.2.txt, YARN-3411.poc.txt
> There is work that's in progress to implement the storage based on a Phoenix 
> schema (YARN-3134).
> In parallel, we would like to explore an implementation based on a native 
> HBase schema for the write path. Such a schema does not exclude using 
> Phoenix, especially for reads and offline queries.
> Once we have basic implementations of both options, we could evaluate them in 
> terms of performance, scalability, usability, etc. and make a call.

This message was sent by Atlassian JIRA

Reply via email to