[jira] [Resolved] (CARBONDATA-3724) Secondary Index enable on partition Table

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (CARBONDATA-3724) Secondary Index enable on partition Table

Akash R Nilugal (Jira)

     [ https://issues.apache.org/jira/browse/CARBONDATA-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kunal Kapoor resolved CARBONDATA-3724.
--------------------------------------
    Fix Version/s: 2.0.0
       Resolution: Fixed

> Secondary Index enable on partition Table
> -----------------------------------------
>
>                 Key: CARBONDATA-3724
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-3724
>             Project: CarbonData
>          Issue Type: New Feature
>            Reporter: Mahesh Raju Somalaraju
>            Priority: Major
>             Fix For: 2.0.0
>
>          Time Spent: 7h 50m
>  Remaining Estimate: 0h
>
> What is Secondary Index table ?
> Currently we have datamaps like, *default datamaps* which are block and blocklet and *coarse grained datamaps* like bloom, and *fine grained datamaps* like lucene
> which helps in better pruning during query. What if we introduce another kind of datamap which can hold blockletId as index? Initial level, we call it as index which
> will work as a child table to the main table like we have MV in our current code.
> The secondary index to carbon table which will be the child table to main table and it can be created on column like we create lucene datamap,
> where we give index columns to create index. In a similar way, we create secondary index on column, so indexes on these column will be blocklet IDs which will
> help in better pruning and faster query when we have a filter query on the index column.
>  
> Existing behaviour:
> Secondary index is not supported for partition table.
> New behaviour:
> Secondary index supports on non partition columns instead of blocking full partition table.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)