You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@carbondata.apache.org by "Kunal Kapoor (Jira)" <ji...@apache.org> on 2020/02/26 08:46:00 UTC

[jira] [Resolved] (CARBONDATA-3723) insert failure when partition column is a first column of projection in MV

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

Kunal Kapoor resolved CARBONDATA-3723.
--------------------------------------
    Resolution: Fixed

> insert failure when partition column is a first column of projection in MV
> --------------------------------------------------------------------------
>
>                 Key: CARBONDATA-3723
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-3723
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: Ajantha Bhat
>            Priority: Major
>             Fix For: 2.0.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> For Alter table drop and add column scenarios, partition columns may not be in the end of create-order column. So, added a logic to keep the partition column in the end in #3634.
>  
> But partition may not be the last projection column during mv creation. So now, create order partition is kept last, but the projection is not last. Hence the insert gives wrong data or fails.
>  
> so, rearrage partition to last in create order columns, only for alter table scenarios



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