[
https://issues.apache.org/jira/browse/SQOOP-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho resolved SQOOP-1709.
---------------------------------------
Resolution: Fixed
Thank you for your contribution [~vybs]!
> 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)
