Enhancements, changed behavior, and resolved issues are provided according to the product version number. When applicable, a component-specific version number is provided for the On-Premises Connector, ODBC driver, or JDBC driver.
The product version number can be obtained from the Hybrid Data Pipeline Web UI by selecting About from the help dropdown.
For On-Premises Connectors, administrators can obtain version information using the Administrator Connectors API. See Obtaining information about On-Premises Connectors for details. In addition, version information can be obtained by opening the On-Premises Connector Configuration Tool and clicking the Version tab.
The JDBC driver version number can be obtained (1) by calling the DatabaseMetaData.getDriverVersion() method or (2) by executing the following command from the driver installation directory:
java -cp ddhybrid.jar com.ddtek.jdbc.ddhybrid.DDHybridDriver.
For the ODBC driver, see Driver version string for details on obtaining the driver version number.
Note: For the latest data source and platform support information, refer to the Product Compatibility Guide.
Key-pair authentication is now supported for Snowflake data sources. For more information, refer to Snowflake parameters.
When using PostgreSQL as a system database, a custom schema may be specified with the PostgreSQL search_path parameter. Refer to External system databases for details.
The Docker image has been enhanced to deploy Hybrid Data Pipeline Docker containers as a non-root user when running Docker on a Linux host. The Docker image has been changed to deploy and run the container with an hdpuser. For more information, refer to Docker deployment steps and Creating the shared file location on Linux.
The Hybrid Data Pipeline server and On-Premises Connector have been upgraded to install and use Tomcat 9.0.98. (On-Premises Connector version 4.6.2.1132)
For On-Premises Connector versions 4.6.2.1132 and later, a JRE is no longer bundled with the installer. Therefore, for successful installation and operation of the On-Premises Connector, a JRE must installed on the host machine, and a JVM must be defined on the system path. Refer to JRE support and integration for details. (On-Premises Connector version 4.6.2.1132)
For JDBC driver versions 4.6.2.436 and later, a JRE is no longer bundled with the JDBC driver installer. Therefore, for successful installation and operation of the OPC a JRE must installed on the host machine, and a JVM must be defined on the system path. Refer to JRE support and integration for details. (JDBC driver version 4.6.2.436)
For ODBC driver versions 4.6.2.356 and later, a JRE is no longer bundled with the ODBC driver installer. For successful installation, a JRE must be installed on your operating system, and the JVM must be defined on your system path. Refer to JRE support and integration for details. (JDBC driver version 4.6.2.356)
The Web UI allowed the caching of account credentials through browser auto-completion.
When using a JDBC third-party connector, the OData schema map could not be refreshed using the Web UI.
Connections from an OData data source to a database server persisted in an idle state when they should have been closed.
When deploying Hybrid Data Pipeline as a Docker container, the license key could not be set using an environment variable. Hybrid Data Pipeline was deployed with the docker run command, but the update.properties file indicated that the instance was unlicensed.
See Hybrid Data Pipeline known issues for details.