[
https://issues.apache.org/jira/browse/HBASE-20237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-20237:
--------------------------
Release Note:
Throw UnknownProtocolException if a client connects and tries to invoke the old
getClosestRowOrBefore method. Pre-hbase-1.0.0 or asynchbase do this instead of
using its replacement, the reverse Scan.
getClosestRowOrBefore was implemented as a flag on Get. Before this patch
though the flag was set, hbase2 were ignoring it. This made it look like a
pre-1.0.0 client was 'working' but then it'd fail finding the appropriate
Region for a client-specified row doing lookups into hbase:meta.
Summary: Put back getClosestRowBefore and throw
UnknownProtocolException instead... for asynchbase client (was: Put back
getClosestRowBefore and throw UnsupportedOperation instead... for asynchbase
client)
> Put back getClosestRowBefore and throw UnknownProtocolException instead...
> for asynchbase client
> ------------------------------------------------------------------------------------------------
>
> Key: HBASE-20237
> URL: https://issues.apache.org/jira/browse/HBASE-20237
> Project: HBase
> Issue Type: Bug
> Components: compatibility, Operability
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20237.branch-2.001.patch
>
>
> asychbase can work against all hbase versions. This fact has saved us a few
> times; e.g. LINE were able to migrate from 0.94 to 1.2 going in part via
> asynchbase and its ability to work against all servers.
> hbase2 breaks this ability of asynchbase. There is nothing for asynchbase to
> figure definitively that it is talking to an hbase2 server (See HBASE-20225).
> Lets add back something it can leverage. HBASE-13954 did a nice job purging
> getClosestRowBefore. Lets put back an RPC stuff that throws an exception if
> it gets called. Thats enough for asynchbase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
