sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boglarka Egyed (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SQOOP-2976) Flag to expand decimal values to fit AVRO schema
Date Wed, 14 Feb 2018 14:37:00 GMT

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

Boglarka Egyed edited comment on SQOOP-2976 at 2/14/18 2:36 PM:

Thanks [~fero] for this improvement! Please don't forget to close the related Review Request.

was (Author: boglarkaegyed):
Thanks [~fero] for this improvement!

> Flag to expand decimal values to fit AVRO schema
> ------------------------------------------------
>                 Key: SQOOP-2976
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2976
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.4.6
>            Reporter: Thomas Scott
>            Assignee: Ferenc Szabo
>            Priority: Major
>             Fix For: 1.5.0
>         Attachments: SQOOP-2976.patch, SQOOP-2976.patch
> As per https://issues.apache.org/jira/browse/AVRO-1864 when importing from Oracle (or
any other database that truncates decimals) Sqoop jobs can fail because the scale of the decimal
produced by the database does not match the scale in the AVRO file.
> For instance if the value 3.15 is produced by Oracle and the AVRO decimal scale  is 3
(this can happen even if the Oracle column is defined with scale of 3) then the job will fail.

> Can we have a flag (--pad-decimals) that pads incoming values with zeros to fit the AVRO
schema (e.g. 3.15 becomes 3.150).

This message was sent by Atlassian JIRA

View raw message