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 01:32:34 UTC

[jira] [Created] (SQOOP-1709) AbstractComplexType changes

Veena Basavaraj created SQOOP-1709:
--------------------------------------

             Summary: AbstractComplexType changes
                 Key: SQOOP-1709
                 URL: https://issues.apache.org/jira/browse/SQOOP-1709
             Project: Sqoop
          Issue Type: Sub-task
            Reporter: Veena Basavaraj
            Assignee: Veena Basavaraj


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)