+1
On Mon, Nov 14, 2016, 3:54 PM sujith chacko
wrote:
> Hi liang,
> Yes, its for high cardinality columns.
> Thanks,
> Sujith
>
> On Nov 14, 2016 2:01 PM, "Liang Chen" wrote:
>
> > Hi
> >
> > I have one query : for no dictionary columns which are high cardinality
> > like phone number, Whether
Hi liang,
Yes, its for high cardinality columns.
Thanks,
Sujith
On Nov 14, 2016 2:01 PM, "Liang Chen" wrote:
> Hi
>
> I have one query : for no dictionary columns which are high cardinality
> like phone number, Whether the pruning cost is hight,or not ?
>
> Regards
> Liang
>
> 2016-11-14 15:18
+1
Hi Liang,
Pruning cost won't be high as block pruning will be done at complete btree
level and it will improve query performance for no dictionary column.
-Regards
Kumar Vishal
On Nov 14, 2016 14:01, "Liang Chen" wrote:
> Hi
>
> I have one query : for no dictionary columns which are high car
Hi
I have one query : for no dictionary columns which are high cardinality
like phone number, Whether the pruning cost is hight,or not ?
Regards
Liang
2016-11-14 15:18 GMT+08:00 sujith chacko :
> Hi All,
>
> I am going to optimize the LIKE Filter query flow for no-dictionary
> columns, pleas
Hi All,
I am going to optimize the LIKE Filter query flow for no-dictionary
columns, please find the details mentioned below.
*Current design:*
For Like filter queries no push down is happening to carbon layer, because
of this there will be no block/blocklet level pruning which can happen
befo