sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Mazak (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SQOOP-1369) Avro export ignores --columns option
Date Thu, 21 May 2015 19:55:19 GMT

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

Paul Mazak edited comment on SQOOP-1369 at 5/21/15 7:55 PM:

Patched for Oracle too.  Addressed code review comments. Updated review board: https://reviews.apache.org/r/34104/

was (Author: pmazak):
Patched for Oracle too.  Addressed code review comments.

> Avro export ignores --columns option
> ------------------------------------
>                 Key: SQOOP-1369
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1369
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Lars Francke
>             Fix For: 1.4.7
>         Attachments: SQOOP-1369.patch, SQOOP-1369_2.patch
> In JdbcExportJob AVRO_COLUMN_TYPES_MAP is being set with the full schema of the output
table. This causes the AvroExportMapper to fail with unknown fields if --columns was used
to restrict the columns to export (it then tries to set a value on the generated class which
doesn't exist).
> There are multiple ways I can see to solve this.
> * Filter the columnTypes passed on to the Mapper in JdbcExportJob.configureInputFormat
> * Pass the --columns value on to the AvroExportMapper and let it ignore things that are
not in there
> * Let AvroExportMapper not fail when it can't set a field.
> I might be able to provide a patch and I'd go with the simplest (the first one probably)
if there are no objections.

This message was sent by Atlassian JIRA

View raw message