You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Eric Lin (JIRA)" <ji...@apache.org> on 2016/10/28 00:24:58 UTC

[jira] [Created] (SQOOP-3040) Lost time millisecond precision for Time data type when importing

Eric Lin created SQOOP-3040:
-------------------------------

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