[
https://issues.apache.org/jira/browse/SQOOP-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079158#comment-13079158
]
Aaron Kimball commented on SQOOP-308:
-------------------------------------
That's a far more invasive change, I think. Everywhere else in Sqoop (read: the
existing ClassWriter) we assume all types are nullable. This would require
modifying the ConnManager API to return nullability for all columns via a new
method named something like "getNullabilityForColumns()" or else incompatibly
changing {{getColumnTypesForQuery()}} to return a complex datatype that
includes nullability and "normal" typing information. (And thus putting a lot
of changes in orm.ClassWriter too.)
> Generated Avro Schema cannot handle nullable fields
> ---------------------------------------------------
>
> Key: SQOOP-308
> URL: https://issues.apache.org/jira/browse/SQOOP-308
> Project: Sqoop
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.3.0
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Fix For: 1.4.0
>
> Attachments: SQOOP-308.patch
>
>
> The generated avro schema for each column is just a primitive type. If a
> database contains a null value, this will fail.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
