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/05/08 17:57:04 UTC

[jira] [Resolved] (CARBONDATA-958) Schema modified time not updated in modifiedtime.mdt when dictionary column is updated to no-dictionary column due to high cardinality

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

Ravindra Pesala resolved CARBONDATA-958.
----------------------------------------
       Resolution: Fixed
         Assignee: Raghunandan S
    Fix Version/s: 1.1.0

> Schema modified time not updated in modifiedtime.mdt when dictionary column is updated to no-dictionary column due to high cardinality
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-958
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-958
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: Raghunandan S
>            Assignee: Raghunandan S
>            Priority: Minor
>             Fix For: 1.1.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Schema modified time not updated in modifiedtime.mdt when dictionary column is updated to no-dictionary column due to high cardinality
> Due to this when we do data loading to same table from multiple spark-submit applications, schema status is not synchronized between applications and hence dictionary file gets generated for high cardinality column also



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)