Hive 1.1 is from 2015, and has a pre 1.0 HBase version.
https://github.com/apache/hive/blob/e60744d017ef79f1b17f474c0b969d4ca5592462/pom.xml#L124

So the exception seems to be justified.

Istvan

On Mon, Sep 9, 2024 at 8:05 AM 张铎(Duo Zhang) <[email protected]> wrote:

> Could you please provide the full stack trace which includes the
> client side code?
>
> We need to find out why we call this method at client side.
>
> Thanks.
>
> Miao Wang <[email protected]> 于2024年9月9日周一 12:05写道:
> >
> >  Hi, community
> >
> >
> >    I access the HBase cluster online by creating an HBase appearance
> using Hive,
> > Hive version: 1.1.0(hbase1.x) Hbase version: 2.4.16. The following
> exception occurred when accessing Hbase:
> >
> >
> > Failed with exception
> java.io.IOException:org.apache.hadoop.hbase.exceptions.UnknownProtocolException:
> org.apache.hadoop.hbase.exceptions.UnknownProtocolException: Is this a
> pre-hbase-1.0.0 or asynchbase client? Client is invoking
> getClosestRowBefore removed in hbase-2.0.0 replaced by reverse Scan.
> > at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:2569)
> > at
> org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:45815)
> > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:392)
> > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:133)
> > at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:354)
> > at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:334)
> >
> >
> >
> >
> > Found that the parameter aaa can be set hbase.meta.replicas.use=true to
> avoid the aforementioned errors,we have not enabled the coprocessor. We are
> only using Hive for simple queries. Can we use the above parameters to
> avoid the issue of inconsistent clients
> >
>


-- 
*István Tóth* | Sr. Staff Software Engineer
*Email*: [email protected]
cloudera.com <https://www.cloudera.com>
[image: Cloudera] <https://www.cloudera.com/>
[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
------------------------------
------------------------------

Reply via email to