Jarek Jarcec Cecho created SQOOP-906:
----------------------------------------
Summary: Sqoop is always calling
ConnectionManager.datetimeToQueryString with TIMESTAMP column type
Key: SQOOP-906
URL: https://issues.apache.org/jira/browse/SQOOP-906
Project: Sqoop
Issue Type: Bug
Affects Versions: 1.4.2
Reporter: Jarek Jarcec Cecho
One user on CDH mailing list has risen
[issue|https://groups.google.com/a/cloudera.org/forum/?fromgroups=#!topic/cdh-user/YEsRyX2Lu-Q]
with incremental import using {{lastmodified}} mode. Sqoop seems to be
generating queries including {{TO_TIMESTAMP}} function even for column that is
defined as {{Types.DATE}}. This is causing issues with Oracle Connector. The
connector seems to be correctly written as appropriate
[OracleManager.datetimeToQueryString|https://github.com/apache/sqoop/blob/trunk/src/java/org/apache/sqoop/manager/OracleManager.java#L575]
seems to be expected condition based on the column type. Unfortunately the
[caller
code|https://github.com/apache/sqoop/blob/trunk/src/java/org/apache/sqoop/tool/ImportTool.java#L280]
is always passing in {{Types.TIMESTAMP}} value instead of the original value.
I think that we should fix that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
