[
https://issues.apache.org/jira/browse/SQOOP-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veena Basavaraj updated SQOOP-1956:
-----------------------------------
Attachment: SQOOP-1956-v2.patch
fixed the integration tests, the reason it was broken, with refactoring we
actually check for integer/ long against schema, in the old code we were not
checking it.
So in Jdbc connector we had not set the INTEGER size and we defaulted it to
LONG and hence the JDBC code failed
> Misc cleanup in the IDF implementation and utils methods
> --------------------------------------------------------
>
> Key: SQOOP-1956
> URL: https://issues.apache.org/jira/browse/SQOOP-1956
> Project: Sqoop
> Issue Type: Sub-task
> Components: sqoop2-framework
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
> Attachments: SQOOP-1956-v1.patch, SQOOP-1956-v2.patch,
> SQOOP-1956.patch
>
>
> Comments from Qian on SQOOP-1901 RB
> https://reviews.apache.org/r/29346/#comment109331
> There are two versions of encodeToCSVLocalDateTime. One will update argument
> and another one will return a string. first one is very tricky to use. It's
> name does not imply the first argument will be changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
