[SQOOP-3460] Sqoop incremental import Upper bound value shall be customised by a query

• Type: New Feature
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.7
• Fix Version/s: 1.5.0
• Component/s: connectors/sqlserver
• Assignee: Dénes Bodó
• Reporter: Dénes Bodó
• Created: 06/Dec/19 07:42
• Updated: 09/Dec/19 08:34

Description

Sqoop incremental import Upper bound value always pick system local time, which is CT zone, but source DB from MSSQL server is using GMT time. Due to this, after the records are being filtered and imported, there are 2000+ records missing.

Here is the upper bound value setup from log:

18/11/20 16:16:30 INFO tool.ImportTool: Lower bound value: '2018-11-20 15:04:08'
18/11/20 16:16:30 INFO tool.ImportTool: Upper bound value: '2018-11-20 16:16:18.05'

Similar issue which was fixed for Oracle: SQOOP-3288.
A similar implementation shall be done for SQLServer.