[ 
https://issues.apache.org/jira/browse/HIVE-9706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated HIVE-9706:
------------------------------
    Attachment: HIVE-9707.1.patch

Prior to patch, running against HBase 1.0.0-SNAPSHOT fails for 
hbase_handler_snapshot.q.

to reproduce (after installing hbase 1.0.0-SNAPSHOT locally):

{code}
hive $> mvn clean -DskipTests -Phadoop-2 -Dhbase.hadoop2.version=1.0.0-SNAPSHOT 
install
hive $> cd itests
itests $> mvn clean -DskipTests -Phadoop-2 
-Dhbase.hadoop2.version=1.0.0-SNAPSHOT install
itests $> cd qtest
qtest $> mvn clean test -Dtest=TestHBaseCliDriver -Phadoop-2 
-Dhbase.hadoop2.version=1.0.0-SNAPSHOT -Dqfile=hbase_handler_snapshot.q
{code}

fails eventually, with hive.log showing an IllegalArgumentException.

after this patch, same steps succeed for both HBase 1.0.0-SNAPSHOT and 0.98.3 
(current version in poms)

> HBase handler support for snapshots should confirm properties before use
> ------------------------------------------------------------------------
>
>                 Key: HIVE-9706
>                 URL: https://issues.apache.org/jira/browse/HIVE-9706
>             Project: Hive
>          Issue Type: Bug
>          Components: HBase Handler
>    Affects Versions: 0.14.0, 1.0.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>             Fix For: 1.2.0, 1.1.0
>
>         Attachments: HIVE-9707.1.patch
>
>
> The HBase Handler's support for running over snapshots attempts to copy a 
> number of hbase internal configurations into a job configuration.
> Some of these configuration keys are removed in HBase 1.0.0+ and the current 
> implementation will fail when copying the resultant null value into a new 
> configuration. Additionally, some internal configs added in later HBase 0.98 
> versions are not respected.
> Instead, setup should check for the presence of the keys it expects and then 
> make the new configuration consistent with them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to