Create a Cloudera Impala connection

  • リリースバージョン: Australia
  • 更新日 2026年03月12日
  • 所要時間:3分
  • Establish a zero copy connection to a Cloudera Impala system in Zero Copy Connector Hub.

    始める前に

    Role required: df_connection_admin

    このタスクについて

    Work with your data source admin to create a connection to Cloudera Impala. For additional information about connecting to Cloudera Impala, refer to the Cloudera Impala documentation.

    手順

    1. Navigate to the available primary connectors in Zero Copy Connector Hub in one of the following ways:
      • Navigate to All > Workflow Data Fabric Hub > Available connectors > Primary connectors.
      • Navigate to Admin > Workflow Data Fabric Hub > Available connectors > Primary connectors.
    2. Find the Cloudera Impala connector and select Connect.
    3. On the form, fill in the fields.
      表 : 1. New Cloudera Impala Connection form
      Field Description
      Name and description
      Connection label Unique name for this connection. This helps in identifying the connection within your system.
      Connection name System-generated name based on the Connection label. This field cannot be modified once the connection is established.
      Short description Description of the connection explaining what it is about.
      Connection attributes
      Connection URL JDBC URL to establish the connection. For example:

      jdbc:cloudera://<host>:<port>;database=<databaseName>

      Authentication methods
      Authentication method Authentication method to use with Cloudera Impala. Default is Basic Authentication.
      User ID User ID associated with the source.
      Password Password associated with the user ID.
    4. Select Connect.

    タスクの結果

    A test connection is made to the external data source, verifying that the connection details are correct and the data source is accessible.

    次のタスク

    If the connection succeeds, configure data steward access on the Access Control tab. See .

    If the connection fails, verify the connection details with your data source administrator and try again.