Release Guide > Part II: Version 10.1.1 > New Features, Changes, and Release Tasks (10.1.1 Update 2) > Changes (10.1.1 Update 2)
  

Changes (10.1.1 Update 2)

This section describes changes in version 10.1.1 Update 2.

Support Changes

This section describes the support changes in version 10.1.1 Update 2.
Distribution support changes for Big Data Management
The following table lists the supported Hadoop distribution versions and changes in 10.1.1 Update 2:
Distribution
Supported Versions
10.1.1 Update 2 Changes
Amazon EMR
5.0.0
No change.
Azure HDInsight
3.5 *
Added support for version 3.5
Dropped support for version 3.4.
Cloudera CDH
5.8, 5.9, 5.10 *
Added support for version 5.10.
Hortonworks HDP
2.3, 2.4, 2.5
Added support for versions 2.3 and 2.4.
IBM BigInsights
4.2
No change.
MapR
5.2
Reinstated support.
Added support for version 5.2.
Dropped support for version 5.1.
*Azure HDInsight 3.5 and Cloudera CDH 5.10 are available for technical preview. Technical preview functionality is supported but is not production-ready. Informatica recommends that you use in non-production environments only.
For a complete list of Hadoop support, see the Product Availability Matrix on Informatica Network: https://network.informatica.com/community/informatica-network/product-availability-matrices
Dropped support for Teradata Connector for Hadoop (TDCH) and Teradata PT objects on the Blaze engine
Effective in version 10.1.1 Update 2, Informatica dropped support for Teradata Connector for Hadoop (TDCH) on the Blaze engine. The configuration for Sqoop connectivity in 10.1.1 Update 2 depends on the Hadoop distribution:
IBM BigInsights and MapR
You can configure Sqoop connectivity through the JDBC connection. For information about configuring Sqoop connectivity through JDBC connections, see the Informatica 10.1.1 Update 2 Big Data Management User Guide.
Cloudera CDH
You can configure Sqoop connectivity through the Teradata PT connection and the Cloudera Connector Powered by Teradata.
  1. 1. Download the Cloudera Connector Powered by Teradata .jar files and copy them to the node where the Data Integration Service runs. For more information, see the Informatica 10.1.1 Update 2 PowerExchange for Teradata Parallel Transporter API User Guide.
  2. 2. Move the configuration parameters that you defined in the InfaTDCHConfig.txt file to the Additional Sqoop Arguments field in the Teradata PT connection. See the Cloudera Connector Powered by Teradata documentation for a list of arguments that you can specify.
Hortonworks HDP
You can configure Sqoop connectivity through the Teradata PT connection and the Hortonworks Connector for Teradata.
  1. 1. Download the Hortonworks Connector for Teradata .jar files and copy them to the node where the Data Integration Service runs. For more information, see the Informatica 10.1.1 Update 2 PowerExchange for Teradata Parallel Transporter API User Guide.
  2. 2. Move the configuration parameters that you defined in the InfaTDCHConfig.txt file to the Additional Sqoop Arguments field in the Teradata PT connection. See the Hortonworks Connector for Teradata documentation for a list of arguments that you can specify.
Note: You can continue to use TDCH on the Hive engine through Teradata PT connections.
Deprecated support of Sqoop connectivity through Teradata PT data objects and Teradata PT connections
Effective in version 10.1.1 Update 2, Informatica deprecated Sqoop connectivity through Teradata PT data objects and Teradata PT connections for Cloudera CDH and Hortonworks. Support will be dropped in a future release.
To read data from or write data to Teradata by using TDCH and Sqoop, Informatica recommends that you configure Sqoop connectivity through JDBC connections and relational data objects.

Big Data Management

This section describes the changes to big data in version 10.1.1 Update 2.

Sqoop

Effective in version 10.1.1 Update 2, you can no longer override the user name and password in a Sqoop mapping by using the --username and --password arguments. Sqoop uses the values that you configure in the User Name and Password fields of the JDBC connection.
For more information, see the Informatica 10.1.1 Update 2 Big Data Management User Guide.

Enterprise Information Catalog

This section describes the changes to the Enterprise Information Catalog in version 10.1.1 Update 2.
Asset path
Effective in version 10.1.1 Update 2, you can view the path to the asset in the Asset Details view along with other general information about the asset.
For more information, see the Informatica 10.1.1 Update 2 Enterprise Information Catalog User Guide.
Business terms in the Profile Results section
Effective in version 10.1.1 Update 2, the profile results section for tabular assets also includes business terms. Previously, the profile results section included column names, data types, and data domains.
For more information, see the Informatica 10.1.1 Update 2 Enterprise Information Catalog User Guide.
URLs as attribute values
Effective in version 10.1.1 Update 2, if you had configured a custom attribute to allow you to enter URLs as the attribute value, you can assign multiple URLs as attribute values to a technical asset.
For more information, see the Informatica 10.1.1 Update 2 Enterprise Information Catalog User Guide.
Detection of CSV file headers
Effective in version 10.1.1 Update 2, you can configure the following resources to automatically detect headers for CSV files from which you extract metadata:
For more information, see the Informatica 10.1.1 Update 2 Live Data Map Administrator Guide.
Amazon Redshift resource
Effective in version 10.1.1 Update 2, you can import multiple schemas for an Amazon Redshift resource.
For more information, see the Informatica 10.1.1 Update 2 Live Data Map Administrator Guide.
Profiling for Hive resource on Data Integration Service
Effective in version 10.1.1 Update 2, you can run Hive resources on Data Integration Service for profiling.
For more information, see the Informatica 10.1.1 Update 2 Live Data Map Administrator Guide.

PowerExchange Adapters for Informatica

This section describes changes to Informatica adapters in version 10.1.1 Update 2.

PowerExchange for Amazon Redshift

Effective in version 10.1.1 Update 2, you can select multiple schemas for Amazon Redshift objects. To select multiple schemas, leave the Schema field blank in the connection properties. In earlier releases, selecting schema was mandatory and you could select only one schema.
If you upgrade to version 10.1.1 Update 2, the PowerExchange for Redshift mappings created in earlier versions must have the relevant schema name in the connection property. Else, mappings fail when you run them on version 10.1.1 Update 2.
For more information, see the Informatica 10.1.1 Update 2 PowerExchange for Amazon Redshift User Guide.