[
https://issues.apache.org/jira/browse/HIVE-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15454065#comment-15454065
]
Lefty Leverenz commented on HIVE-9298:
--------------------------------------
Agreed, it'd be great if Jason could document this and include the limitation
info that [~wzheng] sent me last May:
bq. "Joda DateTime only supports up to millisecond precision, so a custom
timestamp format will only be able to support up to millis precision as opposed
to the default Timestamp format which can support nanosecond precision."
See my 3 Feb. 2015 comment above for wikidocs where this could be documented.
> Support reading alternate timestamp formats
> -------------------------------------------
>
> Key: HIVE-9298
> URL: https://issues.apache.org/jira/browse/HIVE-9298
> Project: Hive
> Issue Type: Improvement
> Components: Serializers/Deserializers
> Reporter: Jason Dere
> Assignee: Jason Dere
> Labels: TODOC1.2
> Fix For: 1.2.0
>
> Attachments: HIVE-9298.1.patch, HIVE-9298.2.patch, HIVE-9298.3.patch
>
>
> There are some users who want to be able to parse ISO-8601 timestamps, as
> well to set their own custom timestamp formats. We may be able to support
> this in LazySimpleSerDe through the use of a SerDe parameter to specify one
> or more alternative timestamp patterns to use to parse timestamp values from
> string.
> If we are doing this it might also be nice to work in support for HIVE-3844,
> to parse numeric strings as timestamp by treating the numeric value as millis
> since Unix epoch. This can be enabled through the SerDe params as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
