You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@carbondata.apache.org by "Ravindra Pesala (JIRA)" <ji...@apache.org> on 2017/12/07 15:53:00 UTC

[jira] [Resolved] (CARBONDATA-1526) 10. Handle compaction in aggregation tables.

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

Ravindra Pesala resolved CARBONDATA-1526.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

> 10. Handle compaction in aggregation tables.
> --------------------------------------------
>
>                 Key: CARBONDATA-1526
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-1526
>             Project: CarbonData
>          Issue Type: Sub-task
>            Reporter: Ravindra Pesala
>            Assignee: Kunal Kapoor
>             Fix For: 1.3.0
>
>          Time Spent: 13h 10m
>  Remaining Estimate: 0h
>
> User can trigger compaction on pre-aggregate table directly, it will further merge the segments inside pre-aggregation table. To do that, use ALTER TABLE COMPACT command on the pre-aggregate table just like the main table. 
> For implementation, there are two kinds of implementation for compaction. 
> 1. Mergable pre-aggregate tables: if aggregate functions are count, max, min, sum, avg, the pre-aggregate table segments can be merged directly without re-computing it.
> 2. Non-mergable pre-aggregate tables: if aggregate function include distinct_count, it needs to re-compute when doing compaction on pre-aggregate table.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)