gt;
>>
>>
>> From: kulkarni.swar...@gmail.com [mailto:kulkarni.swar...@gmail.com]
>> Sent: Wednesday, May 01, 2013 12:17 AM
>>
>>
>> To: user@hive.apache.org
>> Cc: u...@hbase.apache.org
>> Subject: Re: Very poor read performance with composite
***
>
> ** **
>
> *From:* kulkarni.swar...@gmail.com [mailto:kulkarni.swar...@gmail.com]
> *Sent:* Wednesday, May 01, 2013 12:17 AM
>
> *To:* user@hive.apache.org
> *Cc:* u...@hbase.apache.org
> *Subject:* Re: Very poor read performance with composite keys in hbase
: Wednesday, May 01, 2013 12:17 AM
To: user@hive.apache.org
Cc: u...@hbase.apache.org
Subject: Re: Very poor read performance with composite keys in hbase
Rupinder,
Hive supports a filter pushdown[1] which means that the predicates in the where
clause are pushed down to the storage handler level
Rupinder,
Hive supports a filter pushdown[1] which means that the predicates in the
where clause are pushed down to the storage handler level where either they
get handled by the storage handler or delegated to hive if they cannot
handle them. As of now, the HBaseStorageHandler only supports primi
My experience with hive + hbase has been about 8x slower on an average. So I
went ahead with hive only option.
Sent from my iPhone
On Apr 30, 2013, at 11:19 PM, "Rupinder Singh"
mailto:rsi...@care.com>> wrote:
Hi,
I have an hbase cluster where I have a table with a composite key. I map this
To: user@hive.apache.org
Cc: u...@hbase.apache.org
Subject: Re: Very poor read performance with composite keys in hbase
Can you show your query that is taking 700 seconds?
On Tue, Apr 30, 2013 at 12:48 PM, Rupinder Singh
mailto:rsi...@care.com>> wrote:
Hi,
I have an hbase cluster where I
Can you show your query that is taking 700 seconds?
On Tue, Apr 30, 2013 at 12:48 PM, Rupinder Singh wrote:
> Hi,
>
> ** **
>
> I have an hbase cluster where I have a table with a composite key. I map
> this table to a Hive external table using which I insert/select data
> into/from this t
