[
https://issues.apache.org/jira/browse/TAJO-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855446#comment-13855446
]
Keuntae Park edited comment on TAJO-448 at 12/23/13 6:52 AM:
-------------------------------------------------------------
It looks good to me, too.
But, are 32 bits enough to represent unix time?
32 bits unix time only supports up to 2038-01-19 and PostgreSQL looks to
support unix time bigger than 32 bits.
was (Author: sirpkt):
It looks good to me, too.
But, are 32 bits enough to represent unix time?
32 bits unix time only supports up to 2038-01-19 and PostgreSQL looks to
support bigger than 32 bits unix time.
> 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)
