Cloudera Connector for Netezza Release Notes

• Adds support for SLES 12.

• Fixed import in direct mode with multi-schema by removing unnecessary object owner check.
• Added fail fast scenario for import with --as-parquetfile in direct mode.
• Added fail fast scenario for import with --as-avrodatafile in direct mode.

• Added the escapeColName method to handle, for example, column names with lowercase characters.

New argument added:

• --schema: Defines the schema Sqoop uses for both import and export. The schema is used for metadata queries, and for record extraction and loading.

New argument added:

• --nz-uploaddir: Generated Netezza logs will be stored in the HDFS directory specified for this parameter.

• Direct mode now supports extra argument --nz-ctrlchars, that will allow processing data with ASCII characters of value 31 and less.
• Direct mode now supports Sqoop parameters --null-string and --input-null-string that will user allow to override the default NULL substitution character.

• This release updates the connectors package to be compatible with Sqoop 1.4, the version released with CDH4.0.

• This release updated the connectors package to be compatible with Sqoop 1.3, the version released with CDH3u3.
• The connector now supports the LOGDIR directive for Netezza. Refer to the Cloudera Connector for Netezza User Guide for details on how to use this feature.
• The problem of jobs hanging when running import or export against views has been resolved. The connector now displays an error message when used for a job that operates against objects other than regular tables in Netezza.
• Support for the NCHAR datatype has been added in this release.

• This release updated the connectors package to be compatible with Sqoop 1.2, the version released with CDH3u0.
• Updates the Netezza connector to better handle long strings on exports.
• The connector now supports the NVARCHAR type.
• The connector now supports the MAXERRORS directive. Refer to the Cloudera Connector for Netezza User Guide for details on how to use this feature.

When using the Netezza connector in direct mode to import data of type Boolean, the format used by the connector is 'T' or 'F' to represent True or False values. However, when doing an export of data from HDFS to Netezza using the connector in direct mode, the expected Boolean format is 'TRUE' or 'FALSE'.

Workaround: Either convert the data to use 'TRUE'/'FALSE' style representation of Boolean data values prior to doing a direct mode export, or use the regular mode of export instead of direct mode for this type of data.

Expected Resolution: Planned to be fixed in a future release of the connector.