sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Kimball (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-308) Generated Avro Schema cannot handle nullable fields
Date Thu, 04 Aug 2011 01:15:27 GMT

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

Aaron Kimball commented on SQOOP-308:

PS - I think it's perfectly reasonable to do something to improve Sqoop's precision w.r.t.
nullability and typing. But I don't think it's part of this issue. I think that this issue
("the Avro output format is currently broken") is separate from "The Avro output format could
be more precise."

It's also worth considering that since clients of these data files will use the Avro generic
API (as Sqoop doesn't generate a schema file you can turn into a SpecificRecord), end-users
will be dealing with object references returned by {{GenericRecord.get()}} anyway (as opposed
to primitive types), so providing a more precise schema on the nullability doesn't buy you
too much.

> 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


View raw message