tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-448) Timestamp should be based on unixtime
Date Mon, 23 Dec 2013 08:23:50 GMT

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

Hyunsik Choi commented on TAJO-448:
-----------------------------------

Even though It is based on unix time, it can optionally has milliseconds ranging from 0 to
999999999. 32 bits and 64bits all are not enough to represent Timestamp's full representation.
64bit log may be a temporal solution. It may be OK because currently we can only use timestamp
values during query processing, and we cannot store a data including timestamp type to any
file.



> Timestamp should be based on unixtime
> -------------------------------------
>
>                 Key: TAJO-448
>                 URL: https://issues.apache.org/jira/browse/TAJO-448
>             Project: Tajo
>          Issue Type: Bug
>          Components: data type
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.8-incubating
>
>         Attachments: TAJO-448.patch
>
>
> The current timestamp type is based on milliseconds. This patch changes timestamp type
to be based on unixtime.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message