[
https://issues.apache.org/jira/browse/SQOOP-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated SQOOP-1639:
--------------------------------
Attachment: SQOOP-1639.0.patch
Since TEXT doesn't exist as a Java type and we already had LONGVARCHAR, it
looks like the only thing to do is to move CLOB so it will actually map to
Text().
I didn't add any tests here since TEXT doesn't exist in Derby, and the
infrastructure for db-dependent unit tests is on the way in a separate Jira.
> Sqoop2: CLOB data type wrong type
> ---------------------------------
>
> Key: SQOOP-1639
> URL: https://issues.apache.org/jira/browse/SQOOP-1639
> Project: Sqoop
> Issue Type: Bug
> Components: sqoop2-framework
> Affects Versions: 1.99.3
> Reporter: Abraham Elmahrek
> Assignee: Abraham Elmahrek
> Labels: newbie
> Fix For: 1.99.4
>
> Attachments: SQOOP-1639.0.patch
>
>
> The following is incorrect (SqlTypesUtils.java):
> {code}
> case Types.CLOB:
> case Types.FLOAT:
> case Types.REAL:
> case Types.DOUBLE:
> return new FloatingPoint();
> {code}
> CLOB should be Text.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
