Denes Bodo created SQOOP-3460:
---------------------------------
Summary: Sqoop incremental import Upper bound value shall be
customised by a query
Key: SQOOP-3460
URL: https://issues.apache.org/jira/browse/SQOOP-3460
Project: Sqoop
Issue Type: New Feature
Components: connectors/sqlserver
Affects Versions: 1.4.7
Reporter: Denes Bodo
Assignee: Denes Bodo
Fix For: 1.5.0
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:
{noformat}
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'
{noformat}
Similar issue which was fixed for Oracle: SQOOP-3288.
A similar implementation shall be done for SQLServer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
