You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Veena Basavaraj (JIRA)" <ji...@apache.org> on 2014/11/11 02:10:34 UTC
[jira] [Comment Edited] (SQOOP-1708) Rename Unsupported Column type
to DefaultType and add java doc
[ https://issues.apache.org/jira/browse/SQOOP-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205735#comment-14205735 ]
Veena Basavaraj edited comment on SQOOP-1708 at 11/11/14 1:10 AM:
------------------------------------------------------------------
Unknown in fine to me, Un supported seems like a name used when we throw an exception when seeing it. Is that the case? I guess not
if we drop it then it makese sense to cal it unsupported
{code}
break;
case UNSUPPORTED:
ret.put(JDBC_TYPE, ((Unsupported) column).getJdbcType());
break;
{code}
was (Author: vybs):
Unknown in fine to me, Un supported seems like a name used when we throw an exception when seeing it. Is that the case? I guess not
> Rename Unsupported Column type to DefaultType and add java doc
> --------------------------------------------------------------
>
> Key: SQOOP-1708
> URL: https://issues.apache.org/jira/browse/SQOOP-1708
> Project: Sqoop
> Issue Type: Sub-task
> Components: sqoop2-framework
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)