You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/11/13 03:00:15 UTC
[jira] [Commented] (SQOOP-1709) Column Type enhancements for
complex types
[ https://issues.apache.org/jira/browse/SQOOP-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209087#comment-14209087 ]
ASF subversion and git services commented on SQOOP-1709:
--------------------------------------------------------
Commit 100810be41a2c5374ca7629de5d0ec9e5a7e9ea9 in sqoop's branch refs/heads/sqoop2 from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=100810b ]
SQOOP-1709: Column Type enhancements for complex types
(Veena Basavaraj via Jarek Jarcec Cecho)
> Column Type enhancements for complex types
> ------------------------------------------
>
> Key: SQOOP-1709
> URL: https://issues.apache.org/jira/browse/SQOOP-1709
> Project: Sqoop
> Issue Type: Sub-task
> Components: sqoop2-framework
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
> Attachments: SQOOP-1709.patch
>
>
> What is the use case for it to have a "key' as a Column type.
> This mean I could have the key as an Array / Map/ Flaoting point? when would this happen, can String not suffice for the key?
> I need details on this.
> Second, for good reasons, we should have a size field to support the collection size.
> Third, Make sure SchemaSerialization class is updated as well with these changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)