[
https://issues.apache.org/jira/browse/IMPALA-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe McDonnell resolved IMPALA-4687.
-----------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.10.0
commit 50071597a61eefc5afc7a5ce4db56a343172ea44
Author: Joe McDonnell <joemcdonn...@cloudera.com>
Date: Thu Jun 22 17:06:49 2017 -0700
IMPALA-4687: Get Impala working against HBase 2.0
This changes Impala code to tolerate the API differences
between HBase 1.0 and HBase 2.0. It also drops
compatibility code for older HBase versions.
Specific changes:
1. Tolerate return value of Scan for Scan.setCaching()
and Scan.setCacheBlocks(). This has no impact on our code.
2. HBase 2.0 eliminates the ScannerTimeoutException. The
case that previously generated the exception will now
recreate the scanner, so it is not necessary for our code
to recreate the scanner. Short-circuit
HandleResultScannerTimeout on HBase 2.0.
3. HBase 2.0 eliminates the Put.add(), which has been
replaced with Put.addColumn(). This API exists in
HBase 1.0, so it is safe to switch this completely.
This was tested by verifying that an HBase 2.0 cluster
starts up.
Change-Id: I87610e25c01b3547ec332c6975b61284b6837d27
Reviewed-on: http://gerrit.cloudera.org:8080/7277
Reviewed-by: Dan Hecht <dhe...@cloudera.com>
Tested-by: Impala Public Jenkins
> Get Impala working against HBase 2.0 APIs
> -----------------------------------------
>
> Key: IMPALA-4687
> URL: https://issues.apache.org/jira/browse/IMPALA-4687
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Affects Versions: Impala 2.8.0
> Reporter: Tim Armstrong
> Assignee: Joe McDonnell
> Fix For: Impala 2.10.0
>
>
> Currently Impala builds against against the HBase 2.0 APIs but crashes
> immediately upon startup when returning an error from
> HBaseTableScanner::Init() because it tries to find some methods that aren't
> present in the APIs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
