[
https://issues.apache.org/jira/browse/SQOOP-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15640832#comment-15640832
]
Eric Lin commented on SQOOP-3041:
---------------------------------
I am also looking into the issue myself, once a patch is ready, I will upload
to the JIRA.
> Sqoop import TIMESTAMP(6) field into HDFS will truncate tailing zeros in the
> millisecond part
> ---------------------------------------------------------------------------------------------
>
> Key: SQOOP-3041
> URL: https://issues.apache.org/jira/browse/SQOOP-3041
> Project: Sqoop
> Issue Type: New Feature
> Components: tools
> Affects Versions: 1.4.6
> Reporter: Eric Lin
> Priority: Trivial
>
> A column defined as TIMESTAMP(6) will lose it's tailing zeros when imported
> in HDFS:
> Example, the following data with TIMESTAMP(6) data type:
> 2009-11-05 19:01:59.120000
> 2009-11-05 19:01:59.000000
> will become
> 2009-11-05 19:01:59.12
> 2009-11-05 19:01:59.0
> respectively.
> I understand that the values are actually the same as before and we just get
> rid of tailing zeros, however, in some cases we might need to preserve the
> tailing zeros.
> It would be good that Sqoop can leave the data as it is in the original
> database after imported in HDFS
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
