[
https://issues.apache.org/jira/browse/SQOOP-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15642897#comment-15642897
]
Eric Lin commented on SQOOP-3040:
---------------------------------
As part of fix in SQOOP-3039, this JIRA is also fixed. So waiting for
SQOOP-3039 to get approved and committed.
> Lost time millisecond precision for Time data type when importing
> -----------------------------------------------------------------
>
> Key: SQOOP-3040
> URL: https://issues.apache.org/jira/browse/SQOOP-3040
> Project: Sqoop
> Issue Type: Bug
> Components: tools
> Affects Versions: 1.4.6
> Reporter: Eric Lin
>
> To re-produce, create a MySQL database with time(6) data type:
> {code}
> CREATE TABLE `test` (
> `a` time(6) DEFAULT NULL
> ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
> INSERT INTO test VALUES ('16:56:53.099999');
> {code}
> Import the data into Sqoop and data will become "16:56:53", the millisecond
> precision will be lost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
