You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2011/08/04 02:47:27 UTC

[jira] [Commented] (SQOOP-308) Generated Avro Schema cannot handle nullable fields

    [ https://issues.apache.org/jira/browse/SQOOP-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079154#comment-13079154 ] 

Tom White commented on SQOOP-308:
---------------------------------

The change looks good. How about using ResultSetMetaData#isNullable() to test which columns are nullable, and only creating a union schema for those?

> 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