sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkat Ranganathan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3138) Netezza Direct Import does not support --columns options
Date Thu, 23 Feb 2017 16:16:44 GMT

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

Venkat Ranganathan commented on SQOOP-3138:

[~snayakm]  I added you to the contributors and committed it as it was a trivial fix.  Thanks
for your contribution.

Thanks [~BoglarkaEgyed]  for linking the RB to the JIRA

Can you follow up with a test case as  Szaboics Vasas said?   

> Netezza Direct Import does not support --columns options
> --------------------------------------------------------
>                 Key: SQOOP-3138
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3138
>             Project: Sqoop
>          Issue Type: Bug
>          Components: connectors
>    Affects Versions: 1.4.6
>            Reporter: Suraj Nayak
>            Assignee: Suraj Nayak
>            Priority: Minor
>             Fix For: 1.4.7
>         Attachments: SQOOP-3138.patch
> Netezza Direct import Mapper is not sensitive to {{columns}} option. The parameters passed
to {{--columns C1,C2,C3,C4}} are ignored by {{NetezzaExternalTableImportMapper}}. 
> [NetezzaExternalTableImportMapper|https://github.com/apache/sqoop/blob/trunk/src/java/org/apache/sqoop/mapreduce/db/netezza/NetezzaExternalTableImportMapper.java#L83]
on line 83 is based of [output field names| https://github.com/apache/sqoop/blob/trunk/src/java/org/apache/sqoop/mapreduce/db/DBConfiguration.java#L420]
instead of input field names. 
> Even when -D mapreduce.jdbc.output.field.names=C1,C2,C3,C4 is set, another bug in [NetezzaExternalTableImportMapper
@ line 128|https://github.com/apache/sqoop/blob/trunk/src/java/org/apache/sqoop/mapreduce/db/netezza/NetezzaExternalTableImportMapper.java#L128]
duplicates the first column. This is due to the for loop initialization bug where variable
{{i}} should be initialized to {{1}} instead of {{0}}. 

This message was sent by Atlassian JIRA

View raw message