[
https://issues.apache.org/jira/browse/HIVE-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993097#comment-13993097
]
Jason Dere commented on HIVE-4803:
----------------------------------
Might also want to take a look at HIVE-3844, which is also trying to allow
LazyTimestamp to read numeric values. That patch also seems to allow
nanoseconds to be set. However, that patch treats the numeric value as in
seconds since Unix epoch, while your patch treats the value as milliseconds.
I'm not really sure whether secs/msecs is more appropriate here.
> LazyTimestamp should accept numeric values
> ------------------------------------------
>
> Key: HIVE-4803
> URL: https://issues.apache.org/jira/browse/HIVE-4803
> Project: Hive
> Issue Type: Improvement
> Components: Types
> Reporter: Navis
> Assignee: Navis
> Priority: Trivial
> Attachments: HIVE-4803.2.patch.txt, HIVE-4803.D11565.1.patch
>
>
> LazyTimestamp accepts "yyyy-mm-dd hh:mm:ss" formatted string and 'NULL'. It
> would be good to accept numeric form (which is milliseconds).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
