hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kanagha <er.kana...@gmail.com>
Subject Re: Question regarding designing row keys
Date Mon, 03 Oct 2016 22:32:33 GMT
I did an explain plan in Phoenix and it returned as

"Parallel 1-way round robin full scan over metric_table". A full scan is
done.

Thanks

Kanagha

On Mon, Oct 3, 2016 at 1:38 PM, Kanagha <er.kanagha@gmail.com> wrote:

> + user@phoenix.apache.org
>
> Kanagha
>
> On Mon, Oct 3, 2016 at 1:31 PM, Kanagha <er.kanagha@gmail.com> wrote:
>
>> Hi,
>>
>> We have designed an metric_table, for ex:
>>
>> metric_type,
>> timestamp,
>> metricId
>>
>> in HBase using Apache Phoenix. And there is no indexing available on this
>> table yet.
>>
>> Our access patterns are usually
>>
>> select * from metric_table where metric_type='x' and timestamp >
>> 'start_date' and timestamp < 'end_date'.
>>
>> MetricId is not used in select statement.
>>
>> So, how does HBase scanning work in this scenario. I read that each
>> region would hold the start and end rowkey for efficient scanning.
>> In this case, since the rowkey is combined with metricId, will the select
>> statement do a full scan of HBase table?
>>
>> Appreciate any inputs on this.
>>
>> Thanks
>> Kanagha
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message