hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-7805) Support running multiple scans in hbase-handler
Date Sat, 23 Aug 2014 05:00:12 GMT


Hive QA commented on HIVE-7805:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 6123 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed

This message is automatically generated.


> Support running multiple scans in hbase-handler
> -----------------------------------------------
>                 Key: HIVE-7805
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: HBase Handler
>    Affects Versions: 0.14.0
>            Reporter: Andrew Mains
>            Assignee: Andrew Mains
>            Priority: Minor
>         Attachments: HIVE-7805.1.patch, HIVE-7805.patch
> Currently, the HiveHBaseTableInputFormat only supports running a single scan. This can
be less efficient than running multiple disjoint scans in certain cases, particularly when
using a composite row key. For instance, given a row key schema of:
> {code}
> struct<bucket int, time timestamp>
> {code}
> if one wants to push down the predicate:
> {code}
> bucket IN (1, 10, 100) AND timestamp >= 1408333927 AND timestamp < 1408506670
> {code}
> it's much more efficient to run a scan for each bucket over the time range (particularly
if there's a large amount of data per day). With a single scan, the MR job has to process
the data for all time for buckets in between 1 and 100.
> hive should allow HBaseKeyFactory's to decompose a predicate into one or more scans in
order to take advantage of this fact.

This message was sent by Atlassian JIRA

View raw message