[
https://issues.apache.org/jira/browse/SQOOP-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616836#comment-14616836
]
Hudson commented on SQOOP-2370:
-------------------------------
FAILURE: Integrated in Sqoop-ant-jdk-1.6-hadoop20 #1005 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop20/1005/])
SQOOP-2370: Netezza - need to support additional options for full control
character handling (venkat:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=c6627c04cdbc048a193d271c6e94023f921db4e3)
*
src/java/org/apache/sqoop/mapreduce/db/netezza/NetezzaExternalTableExportMapper.java
* src/java/org/apache/sqoop/manager/DirectNetezzaManager.java
* src/docs/user/connectors.txt
> Netezza - need to support additional options for full control character
> handling
> --------------------------------------------------------------------------------
>
> Key: SQOOP-2370
> URL: https://issues.apache.org/jira/browse/SQOOP-2370
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.6
> Reporter: Venkat Ranganathan
> Assignee: Venkat Ranganathan
> Fix For: 1.4.7
>
> Attachments: SQOOP-2370-2.patch, SQOOP-2370.patch
>
>
> SQOOP-2164 and SQOOP-2326 added control character processing capability to
> Netezza external table imports. But in Netezza, carriage return in
> character string is handled by a separater parameter as also handling of nul
> character (ascii 0).
> To fully handle all user requirements, we need to add support for crinstring
> (carriage return in string) and ignore zero (ignore nul char) options to
> Direct loads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
