Create Apache Hive connection

The Apache Hive connection tells Dawiso how to reach HiveServer2. You choose what to scan later, in the data source.

Before you begin, complete Prepare for Apache Hive integration. You need the HiveServer2 host name and port, its transport mode and authentication method, and the scanning account’s credentials.

To create a connection to your system, follow these steps:

1. Navigate to Settings > Data Ingestion > Connections.
2. In the top-right corner, click New connection, find your system, and click Connect.

General configuration

In the general connection configuration step:

1. Name your connection for easier identification in Dawiso. Use a unique, descriptive name, for example a combination of the server name and environment, such as server1_prod.
2. Provide a description of the connection’s purpose.
3. Select a Connection type.
   • Shared: The source is accessible from the public internet, and you can share your credentials with Dawiso.
   • Private: The source isn’t accessible from the public internet, and you can’t share your credentials with Dawiso. For more information, see Create a private connection.
4. Click Next.

Server configuration

In the Server section, provide the following information:

1. Host: The fully qualified domain name of HiveServer2, for example hiveserver2.example.com.
2. Port: 10000 for binary transport, 10001 for HTTP transport, or the port of your gateway. Enter a number only.
3. Transport mode: Select the mode that matches hive.server2.transport.mode on the server:
   • Binary (Thrift): The Hive default.
   • HTTP: Thrift over HTTP.
4. HTTP path: For HTTP transport only. Usually cliservice. Behind an Apache Knox gateway, enter the gateway path.

One HiveServer2 process serves only one transport mode. If the mode doesn’t match the server, the connection test times out or the server closes the connection.

Authentication

In the Authentication section, provide the following information:

1. Authentication: Select the method that matches hive.server2.authentication on the server:
   • None (SASL PLAIN): For NONE.
   • LDAP: For LDAP.
   • Custom / PAM: For CUSTOM, including PAM.
2. Username: The scanning account. The username is required even when the server doesn’t authenticate anyone.
3. Password: The scanning account’s password. Required for LDAP and Custom / PAM. Leave it empty when the server uses NONE. The password is stored encrypted.

All three methods send the username and password the same way: as SASL PLAIN over binary transport, or as HTTP Basic over HTTP transport. The server decides whether it checks them. Kerberos isn’t supported.

Security

In the Security section, select Use SSL/TLS when HiveServer2 runs with hive.server2.use.SSL=true. The setting encrypts the transport and works with every authentication method.

Optional and additional settings

Both Optional Settings and Additional Settings for your connection are optional:

• Optional Settings: Specify options supported by the provider in JSON format.
• Additional Settings: A JSON formatted list of additional settings for troubleshooting or advanced connection configuration. Leave this field empty unless Dawiso support asks you to change it.

Enter optional settings as valid JSON.

Test and save connection

If your connection is shared, click Test connection and wait a few seconds.

• If successful, a green checkmark appears next to the button.
• If it fails, a red error icon appears. Hover over it for a detailed error message. See the troubleshooting section for more information. You can still save the connection.

Finally, click Save and continue to the next step: creating a data source, where you specify what metadata to ingest.

The connection test opens a session, checks that the server is Apache Hive 2.3.0 or later, and lists the databases.

Troubleshooting

Issue	Cause and fix
The test succeeds with an obviously wrong password	Expected when the server runs hive.server2.authentication=NONE, which accepts any credentials. See the warning in Authentication
Authentication fails with a message from Hive	The message comes from HiveServer2 and names the cause, such as a wrong password, an unknown user, or an unreachable directory. Fix what the server reports
The connection times out or the server closes it immediately	Usually the transport mode doesn’t match the server. A binary-mode HiveServer2 doesn’t answer HTTP, and an HTTP-mode one doesn’t answer binary. Check hive.server2.transport.mode and set the matching mode and port. A firewall can cause the same symptom
An error says the transport mode isn’t supported	The transport mode is neither binary nor HTTP. Select Binary (Thrift) or HTTP
An error says the endpoint isn’t an Apache HiveServer2 endpoint	The server is Spark Thrift Server, Databricks in hive_metastore mode, or another Hive-compatible service. Connect to a real HiveServer2, or use the Dawiso integration built for that platform, such as Databricks
An error says the Hive version isn’t supported	The server runs a version older than Hive 2.3.0. Upgrade it, or connect to a newer HiveServer2 that uses the same metastore
An SSL certificate error	The server presents a certificate that the machine running the scan doesn’t trust. Add the issuing certificate authority to that machine’s trust store
The network is unreachable	Hadoop clusters are usually not reachable from the internet. Use a private connection and Dawiso Integration Runtime (DIR) inside your network, and check that its machine can reach the HiveServer2 port

Next, create the Apache Hive data source to choose what to scan and run the first ingestion.