Impala Connector

This node creates a connection to Apache Impala™ via JDBC. You need to provide the server hostname (or IP address), the port, and a database name and specify an authentication mechanism.

This node uses the selected driver's JDBC URL template to create the concrete database URL. Field validation in the dialog depends on whether the (included) tokens referencing them are mandatory or optional in the template.

Options

Connection settings

Database Dialect
Choose the registered database dialect here.
Database Driver

Choose the JDBC driver to connect to the database here. If you select "Use latest driver version available" upon execution the node will automatically use the driver with the latest (highest) driver version that is available for the current database type. This has the advantage that you do not need to touch the workflow after a driver update. However, the workflow might break in the rare case that the behavior of the driver e.g. type mapping changes with the newer version.

If this option is not enabled, you can select a specific version of the registered drivers via the drop-down list. Additional drivers can be registered via KNIME's preference page "KNIME -> Databases". For more details on how to register a new driver see the database documentation.

The node includes the Apache Hive driver, which is compatible with Impala. Proprietary drivers are also supported, but need to be registered first, such as the Impala JDBC connector provided by Cloudera.

Hostname
The hostname (or IP address) of a Impala server. The corresponding driver URL template variable is host.
Port
The port on which the Impala server is listening. The default port is 21,050. The corresponding driver URL template variable is port.
Database name
The name of the database you want to connect to. The corresponding driver URL template variable is database.
None
If checked, then authentication is not required.
Credentials
If checked, the credentials (user and password) are used as defined in the workflow. The credential name links to the specified user and password.
Username
Your username for the database.
Username & password
Your username and password for the database. Note that the password is stored using weak encryption as part the workflow .
Kerberos
Uses an existing Kerberos ticket for authentication. Note that this requires additional parameters to be specified in the JDBC Parameters tab (see below).

JDBC Parameters

This tab allows you to define driver-specific parameters for the JDBC connection. The value of a parameter can be a constant, variable, credential user, credential password or KNIME URL. For more information about the parameters supported by the included Apache Hive driver, please consult the Hive documentation. When using a proprietary Hive driver, please consult the vendor documentation, e.g. Cloudera JDBC Driver for Apache Impala Install Guide.

Kerberos
The following parameters are required to use Kerberos authentication.

Apache Hive Driver (default KNIME driver)

  • kerberosAuthType: fromSubject
  • principal: hive/<server>@<REALM> (replace <server> with the fully qualified hostname and <REALM> with the Kerberos realm of the Hive service).

Proprietary Impala Drivers (provided by Amazon/Hortonworks/Cloudera)

  • AuthMech: 1
  • KrbHostFQDN: full qualified hostname of Impala
  • KrbRealm: REALM (Kerberos realm of Impala)
  • KrbServiceName: impala (Kerberos service name of Impala)

SSL/TLS
The following parameters are required to use SSL/TLS.

Apache Hive Driver (default KNIME driver)

  • ssl: true
  • sslTrustStore: full path of truststore
  • trustStorePassword: password to access the truststore

Proprietary Impala Drivers (provided by Amazon/Hortonworks/Cloudera)

  • SSL: 1
  • SSLTrustStore: full path of truststore
  • SSLTrustStorePwd: password to access the truststore

Advanced

This tab allows you to define KNIME framework properties such as connection handling, advanced SQL dialect settings or logging options.

Input Type Mapping

This tab allows you to define rules to map from database types to KNIME types.

Mapping by Name
Columns that match the given name (or regular expression) and database type will be mapped to the specified KNIME type.
Mapping by Type
Columns that match the given database type will be mapped to the specified KNIME type.

Output Type Mapping

This tab allows you to define rules to map from KNIME types to database types.

Mapping by Name
Columns that match the given name (or regular expression) and KNIME type will be mapped to the specified database type.
Mapping by Type
Columns that match the given KNIME type will be mapped to the specified database type.

Input Ports

This node has no input ports

Output Ports

Icon
A database connection

Popular Predecessors

Popular Successors

Views

This node has no views

Workflows

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.

Installation

To use this node in KNIME, install the extension KNIME Big Data Connectors from the below update site following our NodePit Product and Node Installation Guide:

v5.4

A zipped version of the software site can be downloaded here.

Plugin provider: KNIME AG, Zurich, Switzerland
Plugin version: 5.4.0.v202410141620
On NodePit since: 2024-12-06
Last update: 2024-12-17
KNIME versions: Since v4.0

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!