You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jerry He (JIRA)" <ji...@apache.org> on 2018/08/08 04:14:00 UTC
[jira] [Resolved] (HBASE-19145) Look into hbase-2 client going to
hbase-1 server
[ https://issues.apache.org/jira/browse/HBASE-19145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry He resolved HBASE-19145.
------------------------------
Resolution: Done
> Look into hbase-2 client going to hbase-1 server
> ------------------------------------------------
>
> Key: HBASE-19145
> URL: https://issues.apache.org/jira/browse/HBASE-19145
> Project: HBase
> Issue Type: Task
> Affects Versions: 2.0.0-beta-1
> Reporter: Jerry He
> Assignee: Jerry He
> Priority: Major
>
> From the "[DISCUSS] hbase-2.0.0 compatibility expectations" thread.
> Do we support hbase-2 client going against hbase-1 server?
> We seem to be fine mix-and-match the clients and servers within the
> hbase-1 releases. And IIRC hbase-1 client is ok against 0.98 server.
> Suppose I have a product that depends and bundles HBase client. I
> want to upgrade the dependency to hbase-2 so that it can take
> advantages of and claim support of hbase-2.
> But does it mean that I will need drop the claims that the new version
> of the product support any hbase-1 backend?
> It has not been an objective. It might work doing basic Client API on a
> later branch-1 but will fail doing Admin functions (and figuring if a Table
> is online). If it was a small thing to make it
> work, lets get it in.
> Let's look into it to see what works and what not. Have a statement at least.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)