sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Lin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3040) Lost time millisecond precision for Time data type when importing
Date Fri, 28 Oct 2016 00:25:59 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613778#comment-15613778
] 

Eric Lin commented on SQOOP-3040:
---------------------------------

I am trying to see if I can find a fix. I can't assign it to myself so update the JIRA to
let you know that I am working on it.

> 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)

Mime
View raw message