回复： [Discussion] Support Secondary Index on Carbon Table

[Jacky Li <ja...@qq.com>]

+1 
Thanks for proposing this :)


Regards,
Jacky




------------------ 原始邮件 ------------------
发件人:&nbsp;"Kunal Kapoor"<kunalkapoor642@gmail.com&gt;;
发送时间:&nbsp;2020年2月6日(星期四) 凌晨2:13
收件人:&nbsp;"dev"<dev@carbondata.apache.org&gt;;

主题:&nbsp;Re: [Discussion] Support Secondary Index on Carbon Table



+1

Thanks
Kunal Kapoor

On Wed, Feb 5, 2020, 5:33 PM Indhumathi M <indhumathim27@gmail.com&gt; wrote:

&gt; Hi Community,
&gt;
&gt; Currently we have datamaps like,* default datamaps* which are block and
&gt; blocklet and *coarse grained datamaps* like bloom, and *fine grained
&gt; datamaps* like lucene
&gt; which helps in better pruning during query. What if we introduce another
&gt; kind of datamap which can hold blockletId as index? Initial level, we call
&gt; it as index which
&gt; will work as a child table to the main table like we have MV in our current
&gt; code.
&gt;
&gt; Yes, lets introduce the secondary index to carbon table which will be the
&gt; child table to main table and it can be created on column like we create
&gt; lucene datamap,
&gt; where we give index columns to create index. In a similar way, we create
&gt; secondary index on column, so indexes on these column will be blocklet IDs
&gt; which will
&gt; help in better pruning and faster query when we have a filter query on the
&gt; index column.
&gt;
&gt; Currenlty we will take it as index table and then later part we will make
&gt; it inline to datamap interface.
&gt;
&gt; So design document is attached in JIRA, please give your suggestion/inputs.
&gt;
&gt; JIRA Link: CARBONDATA-3680
&gt; <https://issues.apache.org/jira/browse/CARBONDATA-3680&gt;
&gt;
&gt; Thanks &amp; Regards,
&gt; Indhumathi M
&gt;