hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vrushali C (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage
Date Mon, 27 Apr 2015 22:24:39 GMT

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

Vrushali C commented on YARN-3411:
----------------------------------


Hi [~vinodkv]

bq. Can we make both the implementations use hBase-client from 0.98 irrespective of what the
server uses?

Yes, since hbase 1.0 is both on-wire and on-disk compatible with HBase 0.98.x, I believe we
should be able to use the 0.98 client to write to a hbase 1.0 cluster. But, that means we
would still be using the 0.98 APIs in the timeline writer and would need code changes to move
to 1.0 client. (My current patch uses the new 1.0 APIs). 

Using the 0.98.x client means we won’t be able to take advantage of the 1.0 features which
would really be useful in ATSv2.

thanks
Vrushali

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

Mime
View raw message