You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@carbondata.apache.org by "Raghunandan S (JIRA)" <ji...@apache.org> on 2017/09/06 03:18:00 UTC

[jira] [Commented] (CARBONDATA-1431) Dictionary_Include working incorrectly for date and timestamp data type.

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

Raghunandan S commented on CARBONDATA-1431:
-------------------------------------------

timestamp ans date are of direct dictionary types,For these dictionary files are not created, but dictionary values calculated on the fly.Hence if you include them in DICTIONARY_INCLUDE also they are considered as direct dictionary types and dictionary values calculated on the fly.
 This in my opinion is not an issue to be addressed

> Dictionary_Include working incorrectly for date and timestamp data type.
> ------------------------------------------------------------------------
>
>                 Key: CARBONDATA-1431
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-1431
>             Project: CarbonData
>          Issue Type: Bug
>          Components: sql, test
>    Affects Versions: 1.2.0
>            Reporter: Sangeeta Gulia
>            Assignee: Pallavi Singh
>            Priority: Minor
>             Fix For: 1.2.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> When we create a table with date and timestamp data type with DICTIONARY_INCLUDE : 
> Example : 
> CREATE TABLE uniqdata_INCLUDEDICTIONARY2 (CUST_ID int,CUST_NAME String,ACTIVE_EMUI_VERSION string, DOB timestamp, DOJ timestamp, 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('DICTIONARY_INCLUDE'='CUST_ID,CUST_NAME,ACTIVE_EMUI_VERSION,DOB,DOJ,BIGINT_COLUMN1,BIGINT_COLUMN2')
> It should either create the dictionary for date and timestamp field or it should throw an error that "DICTIONARY_INCLUDE" feature is not supported for date and timestamp.
> whereas in the current master branch,  the query executed successfully without throwing any error and neither it created dictionary files for date and timestamp field.



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