We are pleased to announce the release of Cloudera JDBC 2.6.11 driver for Apache Hive  The release has the following fixes and enhancements:   Enhancements and New Features The driver now supports CDP 7.0   Resolved Issues  [00222028][HIVEJ-610] Queries with a UNION clause are replaced with a UNION ALL clause.   Known Issues  The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.   [HIVEJ-577] The JDBC 4.0 version of the driver fails to connect to servers that require encryption using TLS 1.1 or later.  When you attempt to connect to the server, the connection fails and the driver returns an SSL handshake exception. This issue occurs only when you run the driver using Java Runtime Environment (JRE) 6.0.  As a workaround, run the driver using JRE 7.0 or 8.0.   Workflow Changes See the Release Notes for the full list of upcoming workflow changes that may disrupt the established workflow of the drivers.    Getting Started with the Cloudera Driver Read the Cloudera JDBC 2.6.11 driver for Apache Hive Release Notes and Installation Guide. Download the connector from the Cloudera Connectors page.    As always, we welcome your feedback. Please send your comments and suggestions to the user group through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org. ... View more

We are pleased to announce the release of Cloudera JDBC 2.6.18 driver for Apache Impala.  The release has the following enhancements and fixes:   Enhancements and New Features  [IMPJ-561] The driver now supports Java 11.  [IMPJ-566][IMPJ-580] Updated third-party libraries  The JDBC 4.2 driver has been updated to use the following libraries:  - log4j 2.13.3  - slf4j 1.7.30 The JDBC 4.0 and 4.1 versions of the driver continue to use the previous versions of these libraries. [00221973][IMPJ-569]  The driver now supports the values set via the Statement.setFetchSize API call.   Resolved Issues [00195066][IMPJ-562] The driver converts UPSERT-SELECT to INSERT-SELECT. [00200861][IMPJ-568] When Impala analytic functions are used, the driver does not honor upper-case column aliases. [00206440][IMPJ-576][IMPJ-574] The driver logs incorrect socket timeout values. [00206060][IMPJ-578] When the UseNativeQuery property is set to 1 and there is a  space between "comment" and "show partitions", the driver returns an error.   Known Issues The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.  The JDBC 4.0 version of the driver fails to connect to servers that require encryption using TLS 1.1 or later.  When you attempt to connect to the server, the connection fails and the driver returns an SSL handshake exception. This issue occurs only when you run the driver using Java Runtime Environment (JRE) 6.0.  As a workaround, run the driver using JRE 7.0 or 8.0.   Workflow Changes See the Release Notes for the full list of upcoming workflow changes that may disrupt the established workflow of the drivers.   Getting Started with the Cloudera Driver Read the Cloudera Impala JDBC 2.6.18 Driver for  Apache Impala Release Notes and Installation Guide.  Download the connector from the Cloudera Connectors page.    As always, we welcome your feedback. Please send your comments and suggestions to the user group through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org. ... View more

We are pleased to announce the release of the Cloudera ODBC 2.6.9 Driver for Apache Hive. The release has the following resolved issue.  Enhancements and New Features [00211293][HAR-1156] Updated HiveServer2 connection The driver now supports the Active Passive HS2 Interactive HA mode. For more information, see the Installation and Configuration Guide.  [HAR-1080] macOS X notarization The driver now supports notarization on macOS versions 10.14.6 and later. [HAR-1144] CDH 6.3 support The driver now supports CDH 6.3.  [HAR-1154] CDP 7.0 support The driver now supports CDP 7.0. Resolved Issues [00147018][HAR-1053] On AIX, when using a different OpenSSL version, the driver terminates unexpectedly.  [00220828][HAR-1158] When the SQLBindCol property is called with a NULL pointer, the driver throws an error.  [HAR-1045] In some cases, when attempting to continue an interrupted fetch operation after losing contact with the server, the driver might return result sets with missing rows.  Please refer to the Release Notes for a complete list of new features, resolved issues, known issues, and workflow changes.  For more info on downloading and installing Cloudera ODBC 2.6.9 Driver for Apache Hive, see the links below Download Cloudera ODBC 2.6.9 Driver for Apache Hive Installation Guide As always, we welcome your feedback. Please send your comments and suggestions to the user group through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org. ... View more

We are pleased to announce the release of Cloudera ODBC 2.6.11 driver for Apache Impala.  The release has the following enhancements and fixes:   Enhancements and New Features [IMP-659][00143882] Support for DML result set count The driver now reports the correct row count for DML results in server versions that return the correct row count information. Previously, the driver returned "-1".  [IMP-783] Server-side properties configuration You can now configure server-side properties as driver-wide properties via the registry or the.impalaodbc.ini file.  [IMP-786] Support for CDP 7.0 The driver now supports CDP 7.0.   Resolved Issues  [IMP-662] [00173663] When an incorrect user ID or password is entered in SASL, the driver returns the error message "Error from the Impala Thrift API: No more data to read." This issue has been resolved. The driver now returns a more detailed error message.  [IMP-691][00146553] The driver returns string data untruncated regardless of the value that the string column length is set to. This issue has been resolved. The driver now truncates the string data in the result set if the data exceeds the column length. [IMP-789][00208980] The driver imposes a minimum (255) and maximum (32,767) character length for the StringColumnLength connection property. This issue has been resolved. The minimum limit has been set to 1 and values larger than 32,767 can now be set.   Known Issues The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.    Limited Support for BINARY, DATE, and TIME data types.   BINARY is not a supported data type in Impala.  DATE is supported only when you connect to Impala version 3.3 or later. As a result of the limitations above, some values of TIME data types are also not supported.   Workflow Changes See the Release Notes for the list of upcoming workflow changes that may disrupt the established workflow of the drivers.    Getting Started with the Cloudera Driver Read the Cloudera Impala ODBC 2.6.11 Driver for Impala Release Notes and Installation Guide.  Download the connector from the Cloudera Connectors page.    As always, we welcome your feedback. Please send your comments and suggestions to the user group through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org.   ... View more

We are pleased to announce the release of Cloudera JDBC 2.6.17 driver for Apache Impala.  The release has the following enhancements and fixes:   Enhancements and New Features [IMPJ-547] The driver now supports CDH versions 5.11 through 5.16 and 6.0 through 6.3. [IMPJ-493] The driver now uses version 2.10.1 of the Jackson library. Previously, the driver used Jackson version 2.9.9.   Resolved Issues [00147825][IMPJ-516] The driver does not generate the correct syntax for character parameters in prepared statements if the length of the parameter value is greater than 510. [00147114][IMPJ-512] getParameterMetaData() returns VARCHAR for all parameters. [00147464][IMPJ-514] When you use the com.cloudera.impala.jdbc.DataSource class to connect with the JDBC 4.1 or 4.2 version of the driver, the driver returns a class cast exception. [IMPJ-520] The JDBC 4.1 version of the driver fails to connect to servers that require encryption using TLS 1.2.  This issue has been resolved. However, be aware that this issue still persists for the JDBC 4.0 version of the driver. For more information, see the "Known Issues" section.   Known Issues The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.  The JDBC 4.0 version of the driver fails to connect to servers that require encryption using TLS 1.1 or later.  When you attempt to connect to the server, the connection fails and the driver returns an SSL handshake exception. This issue occurs only when you run the driver using Java Runtime Environment (JRE) 6.0.  As a workaround, run the driver using JRE 7.0 or 8.0.   Workflow Changes See the Installation and Configuration Guide for the full list of workflow changes that may disrupt the established workflow of the drivers.    Getting Started with the Cloudera Driver Read the Cloudera Impala JDBC 2.6.17 Driver for  Apache Impala Release Notes and Installation Guide.  Download the connector from the Cloudera Connectors page.    As always, we welcome your feedback. Please send your comments and suggestions to the user group through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org. ... View more

We are pleased to announce the release of Cloudera JDBC 2.6.10 driver for Apache Hive  The release has the following fixes and enhancements:   Enhancements and New Features [00176863][HIVEJ-584] Updated Thrift library The JDBC 4.2 version of the driver now uses version 0.13.0 of the Thrift library. Previously, this version of the driver used Thrift version 0.12.0. The JDBC 4.0 and 4.1 versions of the driver continue to use Thrift version 0.12.0.  [HIVEJ-575] Updated Jackson library The driver now uses version 2.10.1 of the Jackson library. Previously, the driver used Jackson version 2.9.9.   Resolved Issues [HIVEJ-577] The JDBC 4.1 version of the driver fails to connect to servers that require encryption using TLS 1.2.  [HIVEJ-578] When you invoke the JDBC 4.2 driver with the Datasource class, an exception occurs.  [00176503][HIVEJ-583] When you use the driver with the Denodo application, it returns the following error: "Could not initialize Class".  [HIVEJ-596] In some cases, Hive queries fail with the following error: "com.cloudera.hiveserver2.exceptions.ExceptionConverter.toSQLException: [JDBC Driver]Index: 4, Size: 4"  [HIVEJ-597] SQL statements using the EXISTS predicate return an error.  [HIVEJ-599] The driver returns incorrect results for decimal columns.   Known Issues  The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.   [HIVEJ-577] The JDBC 4.0 version of the driver fails to connect to servers that require encryption using TLS 1.1 or later.    When you attempt to connect to the server, the connection fails and the driver returns an SSL handshake exception. This issue occurs only when you run the driver using Java Runtime Environment (JRE) 6.0. As a workaround, run the driver using JRE 7.0 or 8.0.   Workflow Changes The following changes may disrupt established workflow for the drivers.  In addition to changes that are already implemented in the current version of the driver, this section describes potentially disruptive changes that will be implemented in a future version of the driver, so that you can plan accordingly.   Upcoming Changes *Removing support for JDBC 4 (Java 6). As early as June 2020, the driver will no longer support JDBC 4 (Java 6). For a list of supported JDBC versions, see the Installation and Configuration Guide.   Version 2.6.10 * Beginning with this release, support for JDBC 4.0 (Java 6) has been deprecated.   Support will be removed in a future release. For a list of supported JDBC versions, see the Installation and Configuration Guide.   Version 2.6.1  * Beginning with this release, the driver no longer supports JDBC 3 (Java 5). For a list of supported JDBC versions, see the Installation and Configuration Guide.   Getting Started with the Cloudera Driver Read the Cloudera JDBC 2.6.10 driver for Apache Hive Release Notes and Installation Guide. Download the connector from the Cloudera Connectors page.    As always, we welcome your feedback. Please send your comments and suggestions to the user group through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org. ... View more

We are pleased to announce the release of Cloudera ODBC 2.6.9 driver for Apache Impala.  The release has the following fixes and enhancements: Enhancements and New Features [IMP-704][00174819] Improved performance with multiple concurrent connections.  The driver now retrieves data much faster in scenarios that involve multiple concurrent connections to the data store. This improves performance when working with applications such as Power BI. [IMP-696][IMP-708][IMP-722] Updated third-party libraries. The driver has been updated to use the following libraries: Boost 1.64.0 (previously 1.57.0) libcurl 7.66.0 (previously 7.60.0) Expat 2.2.9 (previously 2.2.0) OpenSSL 1.1.1d (previously 1.1.0j) Resolved Issues [IMP-699][00173163] In some cases, when the driver submits a query that contains a Boolean value expression, the driver returns an "Unsupported query" error.   [IMP-724] The driver terminates unexpectedly when both of the following occur:  Multiple database drivers are loaded to the same process.   One driver unloads and calls ICU's u_cleanup() function, while another driver continues to run and tries to access the memory space that has been cleaned up. Known Issues The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.  Limited Support for BINARY, DATE, and TIME data types.   BINARY is not a supported data type in Impala.  DATE is supported only when you connect to Impala version 3.3 or later. As a result of the limitations above, some values of TIME data types are also not supported. Workflow Changes The following changes may disrupt workflows from earlier versions Version 2.6.8 [IMP-680] Removed support for earlier versions of Impala and CDH.   Beginning with this release, the driver no longer supports Impala 1.0.1 to 2.6 and CDH 5.0 to 5.8. For a list of support versions, see the Installation and Configuration Guide.  Version 2.6.0 Minimum TLS Version Beginning with this release, the driver requires a minimum version of TLS for encrypting the data store connection. By default, the driver requires TLS version 1.2. This requirement may cause existing DSNs and connection strings to stop working, if they are used to connect to data stores that use a TLS version earlier than 1.2. To resolve this, in your DSN or connection string, set the Minimum TLS option (the Min_TLS property) to the appropriate version of TLS for your server. For more information, see the Installation and Configuration Guide. Getting Started with the Cloudera Driver Read the Cloudera Impala ODBC 2.6.9 Driver for Impala Release Notes and Installation Guide.  Download the connector from the Cloudera Connectors page.  As always, we welcome your feedback. Please send your comments and suggestions to the user group through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org. ... View more

We are pleased to announce the release of Cloudera JDBC 2.6.9 driver for Apache Hive  The release has the following fixes and enhancements:   Enhancements and New Features [IMP-636] [00144651][HIVEJ-561][00146044][HIVEJ-563][HIVEJ-554][HIVEJ-539] Updated third-party libraries. The driver now uses the following third-party libraries: jackson 2.9.9 Jackson-datadbind 2.9.9.3 Thrift 0.12.0 ZooKeeper 3.4.14 [HIVEJ-549] Support for JDBC 4.2. The driver now supports JDBC 4.2. For more details see the Installation and Configuration Guide.  [HIVEJ-551] New JDBC class names.  The driver now supports the following class names for Driver and DataSource that are independent of the JDBC version used:    com.cloudera.hive.jdbc.HS1Driver    com.cloudera.hive.jdbc.HS2Driver    com.cloudera.hive.jdbc.HS1DataSource    com.cloudera.hive.jdbc.HS2DataSource The previous JDBC-version-specific class names for 4.0 and 4.1 are still supported.  [00141040][HIVEJ-545] Renaming join columns. By default, the driver does not allow join columns to be renamed. To enable the renaming of join columns, set the RenameJoinColumn property to "true".   Resolved Issues [00146521][HIVEJ-569] The driver resolves the host name to an IP address for SSL verification, causing the host name verification step to fail. [HIVEJ-542] The driver incorrectly treats SSLTrustStore and SSLTrustStorePWD as server-side properties.   Workflow Changes The following changes may disrupt established workflow for the drivers.    In addition to changes that are already implemented in the current version of the driver, this section describes potentially disruptive changes that will be implemented in a future version of the driver, so that you can plan accordingly. Upcoming Changes *Removing support for JDBC 4 (Java 6). Beginning in the fourth quarter of 2019, the driver will no longer support JDBC 4 (Java 6). For a list of supported JDBC versions, see the Installation and Configuration Guide.   Version 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 Read the Cloudera JDBC 2.6.9 driver for Apache Hive Release Notes and Installation Guide. Download the connector from the Cloudera Connectors page.    As always, we welcome your feedback. Please send your comments and suggestions to the user group through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org. ... View more

We are pleased to announce the release of Cloudera ODBC 2.6.8 driver for Apache Impala.  The release has the following fixes and enhancements:   Enhancements and New Features [IMP-636] Updated Impala and CDH support. The driver now supports Impala versions 2.7 through 3.3, and CDH version 5.9 through 5.16 and 6.0 through 6.2 [IMP-666] Support for DATE data type. The driver now supports the DATE data type for Impala version 3.3 and later.  For more information, see “Data Types” in the Installation and Configuration Guide.    Resolved Issues [IMP-686] When an AnalysisException error occurs, the driver incorrectly classifies it as a syntax error and returns SQLState 42000. [IMP-687] After SQLFetech returns and error, if you attempt to call SQLFetch again. The driver terminates unexpectedly.    Known Issues The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.    Limited Support for BINARY, DATE, and TIME data types.   BINARY is not a supported data type in Impala.  DATE is supported only when you connect to Impala version 3.3 or later. As a result of the limitations above, some values of TIME data types are also not supported.   Workflow Changes The following changes may disrupt workflows from earlier versions   Version 2.6.8 [IMP-680] Removed support for earlier versions of Impala and CDH Beginning with this release, the driver no longer supports Impala 1.0.1 to 2.6 and CDH 5.0 to 5.8. For a list of support versions, see the Installation and Configuration Guide.    Version 2.6.0 Minimum TLS Version Beginning with this release, the driver requires a minimum version of TLS for encrypting the data store connection. By default, the driver requires TLS version 1.2. This requirement may cause existing DSNs and connection strings to stop working, if they are used to connect to data stores that use a TLS version earlier than 1.2.   To resolve this, in your DSN or connection string, set the Minimum TLS option (the Min_TLS property) to the appropriate version of TLS for your server. For more information, see the Installation and Configuration Guide.   Getting Started with the Cloudera Driver Read the Cloudera Impala ODBC 2.6.8 Driver for Impala Release Notes and Installation Guide.  Download the connector from the Cloudera Connectors page.    As always, we welcome your feedback. Please send your comments and suggestions to the user group through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org. ... View more

  We are pleased to announce the release of Cloudera ODBC 2.6.7 driver for Apache Impala.  The release has the following fixes and enhancements:   Enhancements and New Features [IMPJ-678] Reporting the maximum length of database fields. You can now specify the maximum character length that the driver reports for the names of the catalogs, columns, schemas, and tables. To do this, st the following connection properties: MaxCatalogNameLen MaxColumnNameLen MaxSchemaNameLen MaxTableNameLen For more information, see the Installation and Configuration Guide. [IMP-634] Thrift transport modes. The driver now enables you to specify the Thrift transport mode used. You can configure the driver to use binary, HTTP, or SASL transport.  [00139411][IMP-668] Updated driver version information in Linux library. You can now check the Linux drivers version from the driver binary file. To do this, open the .so file in a text editor, and search for the text "$driver_version_sb$:". The drivers version number is listed after this text.  [IMP-677] New name of Enable Simulated Transactions. The configuration option Enable Simulated Transactions (key name EnableSimulatedTransactions) has been renamed to Ignore Transactions (key name IgnoreTransactions). The previous key name continues to be supported for backwards compatibility. [IMP-671] Updated third-party library linking for Linux. The Linux driver now statically links to the OpenSSL and ICU libraries by default. Driver builds with dynamically linked libraries continue to be available as needed. For more information about this change, contact Customer Support through https://www.simba.com/support/ [00141891][IMP-645] Internal driver improvements. The driver has been updated with minor internal improvements. [IMP-639] Updated default value for DisableOptimizedEncodingConverter. The DisableOptimizedEncodingConvert property is now set to true by default. This enables the driver to read and replace invalid UTF-8 characters.   Resolved Issues [00142448][IMP-647] When the driver executes a dynamic or parameterized query with OFFSET, it returns an error. This issue has been resolved. The driver now correctly supports LIMIT x,y query syntax. [IMP-654] When query retry is enabled, the driver does not retry queries when a transport or communication link failure occurs. [00144299][IMP-660] When you insert a negative value into a TINYINT column, the driver returns an error. [00144389][IMP-664] When the driver prepares a query that includes a STRING column cast to a variable-length VARCHAR, a length of 32767 is always returned. [IMP-670] When retrieving a DECIMAL value that contains an integer ending with 0, the driver erroneously returns SQL_SUCCESS_WITH_INFO and a truncation error. [00145514][IMP-672] When the driver sets the SQLSetConnectAttr attribute SQL_ATTR_AUTOCOMMIT to SQL_AUTOCOMMIT_OFF, it terminates unexpectedly.   Known Issues The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.    BINARY and DATE data types not supported.  BINARY and DATE are not supported data types in Impala. This also causes some values of TIME data types not to be supported either,    Workflow Changes The following changes may disrupt workflows from earlier versions   Version 2.6.0   Minimum TLS Version Beginning with this release, the driver requires a minimum version of TLS for encrypting the data store connection. By default, the driver requires TLS version 1.2. This requirement may cause existing DSNs and connection strings to stop working, if they are used to connect to data stores that use a TLS version earlier than 1.2.   To resolve this, in your DSN or connection string, set the Minimum TLS option (the Min_TLS property) to the appropriate version of TLS for your server. For more information, see the Installation and Configuration Guide. Getting Started with the Cloudera Driver Read the Cloudera Impala ODBC 2.6.7 Driver for Impala Release Notes and Installation Guide.  Download the connector from the Cloudera Connectors page.    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. ... View more