carbondata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CARBONDATA-37) Support Date/Time format for Timestamp columns to be defined at column level
Date Sun, 09 Oct 2016 00:59:20 GMT

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

ASF GitHub Bot commented on CARBONDATA-37:
------------------------------------------

GitHub user lion-x opened a pull request:

    https://github.com/apache/incubator-carbondata/pull/219

    [WIP] [CARBONDATA-37]Support different time format input style

    # Why raise this PR?
    support different time format input style. In some scenarios different time dimensions
may use different time format, we should support these requirements.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/lion-x/incubator-carbondata timeformat

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-carbondata/pull/219.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #219
    
----
commit 15d1e640f96b15411fb39eaf7208b3b656ebda0a
Author: X-Lion <xlion.pku@gmail.com>
Date:   2016-09-29T14:33:18Z

    Lionx0929

----


> 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)

Mime
View raw message