Table of Contents

Search

  1. Preface
  2. Part 1: Hadoop Integration
  3. Part 2: Databricks Integration
  4. Appendix A: Connections Reference

Replace Hive Run-time Connections with Hadoop Connections

Replace Hive Run-time Connections with Hadoop Connections

Effective in version 10.2.2, Big Data Management dropped support for the Hive engine and Hive run-time connections. If you used Hive connections to run mappings on the Hadoop cluster, you must generate Hadoop connections from the Hive connections.
Perform this task in the following situations:
  • You upgraded from version 10.1.1 or earlier.
  • The Hive connections are configured to run mappings in the Hadoop environment.
The upgrade process generates a connection name for the Hadoop connection and replaces the connection name in the mappings. It does not create the physical connection object. When the upgrade is complete, you must run a command to generate the connection. You generate Hadoop connections from Hive connections that are configured to run mappings in the Hadoop environment.
You must generate Hadoop connections from Hive connections that are configured to run mappings in the Hadoop environment.
  1. Run
    infacmd isp generateHadoopConnectionFromHiveConnection
    to generate a Hadoop connection from a Hive connection that is configured to run in the Hadoop environment.
    The command names the connection as follows: "Autogen_<Hive connection name>." If the connection name exceeds the 128 character limit, the command fails.
  2. If the command fails, perform the following tasks:
    1. Rename the connection to meet the character limit and run the command again.
    2. Run
      infacmd dis replaceMappingHadoopRuntimeConnections
      to replace connections associated with mappings that are deployed in applications.
    3. Run
      infacmd mrs replaceMappingHadoopRuntimeConnections
      to replace connections associated with mappings that you run from the Developer tool.
  3. If the Hive connection was parameterized, you must update the connection names in the parameter file. Verify that the Hive sources, Hive targets, and the Hive engine parameters are updated with the correct connection name.
  4. If any properties changed in the cluster, such as host names, URIs, or port numbers, you must update the properties in the connections.
For information about the infacmd commands, see the
Informatica® Command Reference
.