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

Posted to dev@sqoop.apache.org by "Gwen Shapira (JIRA)" <ji...@apache.org> on 2015/03/23 22:00:53 UTC

[jira] [Commented] (SQOOP-2252) Add default to Avro Schema

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

Gwen Shapira commented on SQOOP-2252:
-------------------------------------

Thats a good point, I've ran into similar issue myself.

Are you planning on attempting to provide a patch? 

Also, do you think we should set the schema with default of null only in cases where the original DB has "nullable" fields, or for every field (even if its "non-null" in the original)?

> Add default to Avro Schema
> --------------------------
>
>                 Key: SQOOP-2252
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2252
>             Project: Sqoop
>          Issue Type: Improvement
>          Components: tools
>    Affects Versions: 1.4.5
>            Reporter: Andrew Stevenson
>            Priority: Minor
>
> Currently no default value is set on the avro schemas. Setting a default value is required for schema evolution.
> I currently have to rewrite the schema to be a union on [null: type] rather than [type:nulll] and add null as a default in other to update kite datasets.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)