carbondata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Indhumathi Muthumurugesh (Jira)" <j...@apache.org>
Subject [jira] [Updated] (CARBONDATA-3680) Support secondary index on carbon table
Date Wed, 05 Feb 2020 12:03:00 GMT

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

Indhumathi Muthumurugesh updated CARBONDATA-3680:
-------------------------------------------------
    Attachment: SI doc.pdf

> Support secondary index on carbon table
> ---------------------------------------
>
>                 Key: CARBONDATA-3680
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-3680
>             Project: CarbonData
>          Issue Type: New Feature
>            Reporter: Indhumathi Muthumurugesh
>            Priority: Major
>         Attachments: SI doc.pdf
>
>
> 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.
> Yes, lets introduce 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.



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

Mime
View raw message