[
https://issues.apache.org/jira/browse/SQOOP-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549219#comment-14549219
]
Sqoop QA bot commented on SQOOP-1369:
-------------------------------------
Testing file
[SQOOP-1369.patch|https://issues.apache.org/jira/secure/attachment/12730924/SQOOP-1369.patch]
against branch sqoop2 took 0:00:09.215420.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to apply patch (exit code 128):
{code}fatal: corrupt patch at line 85
{code}
{color:green}SUCCESS:{color} Clean was successful
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1358/console].
This message is automatically generated.
> 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.99.7
>
> Attachments: SQOOP-1369.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
(v6.3.4#6332)
