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.kana...@gmail.com> wrote: > + user@phoenix.apache.org > > Kanagha > > On Mon, Oct 3, 2016 at 1:31 PM, Kanagha <er.kana...@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 >> > >
