Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- relates to
-
SQOOP-2921 support for nested data types
- Open
- links to