[ 
https://issues.apache.org/jira/browse/CARBONDATA-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823733#comment-15823733
 ] 

Mohammad Shahid Khan commented on CARBONDATA-641:
-------------------------------------------------

date and timestamp type are direct dictionary column, so automatically no 
dictionary file will be generated for the same.
Therefor DATE and TIMESTAMP both should not be supported in DICTIONARY_EXCLUDE 
option.

Input validation for the timestamp type is missing i.e. its not throwing error 
for the same.
Solution:
Validation should be added for the timestamp type as well.
After fix both the adding both type date and timestamp in DICTIONARY_EXCLUDE 
will throw error.

> DICTIONARY_EXCLUDE is not working with 'DATE' column
> ----------------------------------------------------
>
>                 Key: CARBONDATA-641
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-641
>             Project: CarbonData
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0.0-incubating
>         Environment: Spark - 1.6 and Spark - 2.1
>            Reporter: Anurag Srivastava
>
> I am trying to create a table with *"DICTIONARY_EXCLUDE"* and this property 
> is not working for *"DATE"* Data Type.
> *Query :*  CREATE TABLE uniqdata_date_dictionary (CUST_ID int,CUST_NAME 
> string,ACTIVE_EMUI_VERSION string, DOB date, DOJ date, BIGINT_COLUMN1 
> bigint,BIGINT_COLUMN2 bigint,DECIMAL_COLUMN1 decimal(30,10), DECIMAL_COLUMN2 
> decimal(36,10),Double_COLUMN1 double, Double_COLUMN2 double,INTEGER_COLUMN1 
> int) STORED BY 'org.apache.carbondata.format' TBLPROPERTIES 
> ("TABLE_BLOCKSIZE"= "256 MB","DICTIONARY_EXCLUDE"="DOB,DOJ");
> *Expected Result :* Table created.
> *Actual Result :* Error: 
> org.apache.carbondata.spark.exception.MalformedCarbonCommandException: 
> DICTIONARY_EXCLUDE is unsupported for date data type column: dob 
> (state=,code=0)
> But is is working fine, If I use 'TIMESTAMP' in place of 'DATE'.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to