Zhijie Shen commented on YARN-3411:

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

I guess it's not the client problem, but the server problem. To use Phoenix, 
HBase daemon needs to start with Phoenix server lib installed. That said, we 
won't be able to have a HBase 1.0 cluster which has installed 4.3 Phoenix.

And given Vrushali's comment "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." is right, I guess the client should 
probably be fine instead. 4.3 Phoenix client uses HBase 0.98.x client, such 
that it can talk to HBase 1.0 server.

> [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