[
https://issues.apache.org/jira/browse/CARBONDATA-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564389#comment-15564389 ]
ASF GitHub Bot commented on CARBONDATA-37:
------------------------------------------
Github user QiangCai commented on a diff in the pull request:
https://github.com/apache/incubator-carbondata/pull/219#discussion_r82720457
--- Diff: processing/src/main/java/org/apache/carbondata/processing/surrogatekeysgenerator/csvbased/CarbonCSVBasedSeqGenStep.java ---
@@ -1171,6 +1171,14 @@ else if(isComplexTypeColumn[j]) {
DirectDictionaryGenerator directDictionaryGenerator1 =
DirectDictionaryKeyGeneratorFactory
.getDirectDictionaryGenerator(details.getColumnType());
--- End diff --
If the column type is TimeStamp, please provide dateformat to KeyGenerator.
Better to provide different key generator for each date format.
> Support Date/Time format for Timestamp columns to be defined at column level
> ----------------------------------------------------------------------------
>
> Key: CARBONDATA-37
> URL:
https://issues.apache.org/jira/browse/CARBONDATA-37> Project: CarbonData
> Issue Type: Improvement
> Reporter: Vimal Das Kammath
> Assignee: Lionx
>
> Carbon support defining the Date/Time format. But the configuration for the same is present in carbon.properties and hence is global for all tables.
> This global configuration for timestamp format cannot support scenarios where different tables or different Timestamp columns in the same table.
> Suggest to provide option in the create table DDL itself to define the format for each Timestamp column. Also provide defaults so that users can create table with Timestamp columns without having to always define the Date/Time format.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
