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 now supports user authentication using the SSO/SAML protocol. Customers can configure SAML authentication by providing the details of an identity provider and can configure users to use the SAML authentication.
When the "FileNotFoundException (Too many open files)" error occurred, the Hybrid Data Pipeline connection was lost and the server had to be restarted.
When fetching invalid date and datetime values from columns or literals, such as SELECT DATE(0), against MySQL data sources, the Hybrid Data Pipeline server returned an error.
Tableau was unable to connect to OData v4 endpoints exposed by Hybrid Data Pipeline.
Users were unable to use special characters for Hybrid Data Pipeline passwords.
When HTTP was disabled on the load balancer, the load balancer did not return OData responses to the client application as would be expected with the configuration of the X-Forwarded-Proto header to manage HTTP and HTTPS traffic.
See Hybrid Data Pipeline known issues for details.