These release notes provide enhancements, changed behavior, and resolved issues. 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.
The JDBC connection property SpyAttributes has been updated to exclude the attribute load=classname, which was previously used to load the driver specified by the given class name. If a log file name does not include the .log extension, the driver automatically appends it. (JDBC driver 4.6.2.1023)
When upgrading from Hybrid Data Pipeline version 4.6.2.2978 to version 4.6.2.3275, deployment failed because the schema update script assumed a specific index name that did not match the existing one.
When connecting to Hybrid Data Pipeline via JDBC with SSL enabled on Java 17, the validateservercertificate=false property was ignored, causing the SSL connection to fail due to server certificate validation. (JDBC driver 4.6.2.1023)
See Hybrid Data Pipeline known issues for details.