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.
The On-Premises Connector version number 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.
Hybrid Data Pipeline has been enhanced to support Google Analytics, Google BigQuery, Salesforce, and REST data store implementations of OAuth 2.0. To integrate Hybrid Data Pipeline with an OAuth 2.0 authorization flow, Hybrid Data Pipeline must be registered as a client application with the given data store. Then, OAuth application and profile objects must be created to manage OAuth endpoints, properties, and tokens. For details, refer to Integrating Hybrid Data Pipeline as a client application with a data store OAuth 2.0 authorization flow. (On-Premises Connector 18.104.22.168)
The procedures for integrating Hybrid Data Pipeline as a client application to enable access to Google Analytics include the ability to select or create an OAuth application in the Web UI. For details, refer to Google Analytics parameters.
When selecting a data source from the dropdown in the SQL Editor, the server is returning the error "No suitable driver found."
When performing an insert on an OData-enabled MySQL Community Edition data source, Hybrid Data Pipeline returned an error on a datetime column.
Performing a mergeEntity operation against an OData-enabled MySQL Community Edition data source resulted in a NullPointerException.
Server-side SSL could not be configured because the enable_ssl.sh script was not properly setting the truststore information from the Web UI.
To mitigate the CVE-2022-23181 security vulnerability, the Tomcat context.xml file has been modified
such that session persistence is disabled by default.
See Hybrid Data Pipeline known issues for details.