[SQOOP-3040] Lost time millisecond precision for Time data type when importing

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.6
• Component/s: tools
• Assignee: Eric Lin
• Reporter: Eric Lin
• Created: 28/Oct/16 00:24
• Updated: 16/Jan/17 05:51

Description

To re-produce, create a MySQL database with time(6) data type:

CREATE TABLE `test` (
  `a` time(6) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

INSERT INTO test VALUES ('16:56:53.099999');

Import the data into Sqoop and data will become "16:56:53", the millisecond precision will be lost.

Issue Links

• is part of: SQOOP-3039 Sqoop unable to export Time data "13:14:12.1234" into Time colum in RMDBS