We are pleased to announce the release of Cloudera JDBC 2.6.15 driver for Apache Impala. The release has the following fixes and enhancements:
Enhancements and New Features
- [IMPJ-489] Default port - If a port is not specified in the connection URL, the driver now uses a default port depending on the specified transport mode:
- If the transport mode is set to HTTP, the driver uses port 28000 as the default.
- If the transport mode is est to SASL or binary, or is not specified, the driver uses port 21050 as the default.
- [IMPJ-487] HTTP header host name - When the driver uses HTTP header, the header now uses the host name instead of the resolved IP address.
Resolved Issues
- [IMPJ-488] If AuthMech is set to 0 and UID and PWD are specified in the connection URL, the username and password are not sent to the server. This has now been resolved. Now, if UID or PWD are specified in the connection URL, the driver always sends them to the server.
Workflow Changes
The following are breaking changes to driver functionality. These changes may cause some workflows from earlier versions to fail.
2.6.15 - New default port
- Beginning with this release, if the port is not specified in the connection URL, the driver uses a default port depending on the specified transport mode.
- If the transport mode is set to HTTP, the driver uses port 28000 as the default.
- If the transport mode is est to SASL or binary, or is not specified, the driver uses port 21050 as the default.
2.6.1 - Removed support for JDBC 3 (Java 5)
- Beginning with this release, the driver no longer supports JDBC 3 (Java 5). Only JDBC 4 (Java 6) and JDBC 4.1 (Java 7) are supported.
Getting Started with the Cloudera Driver
As always, we welcome your feedback. Please send your comments and suggestions to the user group of through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org.
