We are pleased to announce the release of Impala JDBC v2.5.32 driver. This release has the following fixes and enhancements:
- Enhancements and new features:
- Support added for optimizing driver performance for INSERT statements.
You can use the new Optimized Insert connection property to optimize driver performance when executing INSERT statements. This optimization is enabled by default. - Support added for configuring the Thrift transport protocol.
You can use the new transport Mode connection property to specify the transport protocol that the driver uses in the Thrift layer. The default AuthMech value now depends on the transport Mode setting. For more information, see the Cloudera JDBC Driver for Impala Installation and Configuration Guide. - Implemented server version checking for the getTypeInfo() method.
When you call the getTypeInfo() method, the driver now checks the version of the Impala server that you are connecting to and only returns data types that are supported by that Impala version.
- Issues resolved:
- When using a single statement to insert multiple rows, an OutOfMemory error occurs.
- In some cases, when assertions are enabled and an error occurs, the driver returns an assertion error instead of the appropriate error.
- The driver incorrectly reports the buffer length and octet length of CHAR and VARCHAR data as 0.
- In some cases, the driver returns a negative value for column size.
- The data type names returned by the getTypeInfo() method are different from the data type names used in Impala.
See Release Notes for JDBC for details on all of the fixes.
Getting Started with the Cloudera Drivers
As always, we welcome your feedback. Please send your comments and suggestions to the user group or through our community forums. You can also file bugs through our external JIRA projects on issues.cloudera.org.
