[
https://issues.apache.org/jira/browse/SQOOP-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205895#comment-14205895
]
Jarek Jarcec Cecho commented on SQOOP-1709:
-------------------------------------------
Yes you are correct that the property {{key}} in class {{AbstractComplexType}}
represents the inner type stored in the complex type. Do note that we currently
have four complex types - {{Set}}, {{Array}}, {{Enum}} and {{Map}} from which
the first three are incorporating only one subtype whereas the last one do have
two subtypes (key and value).
I'm fine with introducing an {{AbstractPrimitive}} class to limit the "key" in
the map. I would suggest to do this by switching the {{AbstractComplexType}} to
contain Map's value (and hence {{Column}}) whereas the class Map will contain
the Map's key (and hence {{AbstractPrimitive}}).
> AbstractComplexType changes
> ---------------------------
>
> 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
>
>
> 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)
