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 "Li Lu (JIRA)" <ji...@apache.org> on 2015/03/27 21:15:53 UTC

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

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

Li Lu commented on YARN-3411:
-----------------------------

Hi [~vrushalic], thanks for working on this! It would be good for us to have both hbase and Phoenix storage implementations for comparison. Just keeping a record here that I think we can do the evaluation, before we move into implementing the aggregations. In this way we may save duplicated efforts in designing and implementing aggregations. 

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