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

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 Read the Cloudera Impala JDBC 2.6.15 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

We are pleased to announce the release of Cloudera JDBC v2.6.12 driver for Apache Impala. The release has the following resolved issues:   Resolved Issues [00142091][IMPJ-461] The driver casts empty string to CHAR(0), causing issues on the server. This issue has been resolved. The driver new casts empty strings to CHAR(0). [00141482] [IMPJ-468] The driver executes UPSERT queries incorrectly, causing errors to be shown.   Workflow Changes The following are breaking changes to driver functionality. These changes may cause some workflows from earlier versions to fail.   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 Impala JDBC 2.6.12 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

We are pleased to announce the release of Cloudera JDBC v2.6.11 driver for Apache Impala. The release has the following resolved issues and enhancements:   Enhancement and New Features [00141482][IMPJ-458] Improved performance of prepared statements with large numbers of parameters. Preparing statements no longer takes exponentially more time for each parameter. Additionally, DatabaseMetaData.supportsBatchUpdates() now returns true. [00138441][IMPJ-443] Always pass UID parameter to server. If the UID parameter is specified in the connection URL, the driver now passes it to the server even when No Authentication is specified (AuthMech=0). [IMPJ-448] The driver now supports Impala versions 1.0.1 through 3.1, and CDH versions 5.0 through 5.16 and 6.0 through 6.1. [00140157][IMPJ-450] The driver now uses version 0.12.0 of the Thrift library.   Resolved Issues [00141235] [IMPH-454] The driver incorrectly treats SSLTrustStore and SSLTrustStorePWD as server-side properties. [IMPJ-444] If a SQL query ends in a semicolon, the driver reports an error. This issue has been resolved. The driver now removes trailing semicolons from queries before sending 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.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 Impala JDBC 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 of 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 v2.6.5 driver for Apache Impala.  The release has the following fixes and enhancements:   Enhancements & New Features [IMP-573] On macOS, you can now use the driver with version 2.3.1 of unixODBC driver manager. [IMP-628] The driver now uses OpenSSL 1.1.0j. [IMP-609] The driver now supports Impala versions 1.0.1 through 3.1, and CDH versions 5.0 through 5.16 and 6.0 through 6.1.   Resolved Issues [00141430][IMP-623] In some cases, queries with a parameterized insert fail. [00141992][IMP-629] The driver does not handle scale and precision of decimal type correctly. [IMP-612] Driver does not pass a UID into the session when connected using No Authentication. [IMP-631 ] The driver incorrectly translates CHAR and VARCHAR types of INSERT values to CAST(CAST(...)). This issue is resolved. The driver now translates these values to a single CAST.   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 v2.6.5 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

We are pleased to announce the release of the Cloudera ODBC v2.6.4 Driver for Apache Hive  The release has the following new features and resolved issues.   Enhancements and New Features [00135108][HAR-921] The driver now supports cookie-based authentication as part of the authentication process. [HAR-965] The driver has been updated to use version 1.1.0 of the RapidJSON parser. [HAR-937] To reduce the footprint of the Linux driver, the OpenSSL and ICU libraries are now dynamically linked.   Resolved Issues [00138945][HAR-959] When SQLTables is called, the driver does not correctly display views. [HAR-926] The driver fails to parse queries that contain the keyword “LIMIT”. [00136282][HAR-936] The driver fails to parse queries that contain a non-reserved keyword as the column name.   Please refer to the Release Notes for a complete list of new features and resolved issues.   For more info on downloading and installing Cloudera ODBC v2.6.4 Driver for Apache Hive, see the links below Download Cloudera ODBC 2.6.4 Driver for Apache Hive Installation Guide 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

We are pleased to announce the release of Cloudera ODBC v2.6.4 driver for Apache Impala.  The release has the following fixes and enhancements:   Enhancements & New Features [0013885][IMP-601] The driver now supports the use of SERVER as an alias for the HOST configuration options. The configuration option HOST is still supported.   [IMP-607] The driver has been updated to use version 1.1.0 of the RapdJSOn parser.   Resolved Issues [00139182][IMP-603] in some queries that include aliases in subqueries, the driver translates the query to a syntax that is not supported by Impala CDH6.   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 v2.6.4 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

We are pleased to announce the release of Cloudera JDBC v2.6.9 driver for Apache Impala. The release has the following resolved issues: Resolved Issues [00137281][IMPJ-437] After a query fails on the server side, subsequent   queries on driver side also fail. Breaking Changes The following are breaking changes to driver functionality. These changes may cause some workflows from earlier versions of the driver to fail. 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 for Apache Impala Read the Release Notes and Installation Guide for Cloudera JDBC v2.6.9 Driver for Apache Impala 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

We are pleased to announce the release of Cloudera ODBC v2.6.2 Driver for Apache Impala.  The release has the following fixes and enhancements:   Resolved Issues: [00134149] [IMP-565] The driver reports transport-related errors using the generic error code 10000, instead of reporting them more specifically using error code 08S01   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 ODBC v2.6.2 Drive for Apache Impala 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

We are pleased to announce the release of Hive JDBC v2.6.5. The release has the following fixes and enhancements: Resolved Issues [00139103][HIVEJ-534] If a SQL query ends in a semicolon, the driver reports an error. This issue has been resolved. The driver now removes trailing semicolons from queries before sending them to the serve r. Breaking Changes The following are breaking changes to driver functionality. Thee changes may cause some workflow from earlier versions of the driver to fail. 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.5 Driver for 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 of through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org. ... View more

  Dear CDH, Cloudera Manager, and Cloudera Navigator users,   We are pleased to announce the release of Cloudera Enterprise 6.0.1 (CDH 6.0.1, Cloudera Manager 6.0.1, and Cloudera Navigator 6.0.1).   This release fixes key bugs and includes the following:   The following upstream issues are fixed in CDH 6.0.1: Rebase to HBase 2.0.2 HDFS-10240 - Fixed an issue where the race between close/recoverLease leads to missing blocks. HDFS-10453 - Fixed an issue where the ReplicationMonitor thread could get stuck for a long time due to the race between replication and delete of the same file in a large cluster. SOLR-12450 - Don't allow referral to external resources in various config files. HDFS-13281 - Fixed an issue where the Namenode#createFile was not /.reserved/raw/ aware. HADOOP-15698 - Fixed an issue where the KMS log4j is not initialized properly at startup. OOZIE-3193 - Applications are not killed when submitted via subworkflow. FLUME-3237 - Handling RuntimeExceptions coming from the JMS provider in JMSSource. HUE-8467 - Queries from ImpalaDaemonApi failing when Impala is configured with webserver_htpassword. For a full list of upstream JIRAs fixed in CDH 6.0.1, see the issues fixed section of the Release Notes . Cloudera Manager fixes for the following issues: X-Frame-Options not set in latest C6 Auto-TLS support for commands like Oozie's Upload Sharelib CDH upgrade fails with checkJavaComponent(DbHostHeartbeat.java:177) CDH 6.0.0 upgrade validator fails when no Sentry service is available Agent install fails with "Installing hue-plugins package" CDH Upgrade fails to delete Solr data from HDFS Cloudera Manager wizard shows CDH 5.15.0 as a package choice Host inspector shows psycopg2 version error even after psycopg2-2.6.2 is installed Fix display vcore and memory values when they are not integers Upgrade Service Inspector shows it passed, but the solr check failed Diagnostic bundles now contain the DB_READ_LATENCY metric Improved the performance of the Service Monitor by reducing memory consumption Added an upgrade check from CDH 5 to CDH 6 to check if HBase tables are using PREFIX_TREE_ENCODING For a full list of issues fixed in Cloudera Manager 6.0.1 , see th e new issues and issues fixed section of the Release Notes . We look forward to you trying the new release by using the information below: Download Cloudera Enterprise View the documentation   As always, we are happy to hear 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 . ... View more

We are pleased to announce the release of Hive ODBC v2.6.1. The release has the following resolved issue.   Resolved Issues [00119275][HAR-833] CAST AS VARCHAR(n) returns incorrect metadata.   Getting Started with the Cloudera Driver Read the Cloudera Hive ODBC 2.6.1 Driver for 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 of 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 Impala ODBC v2.6.0.  The release has the following fixes: Enhancements and New Features: [IMP-478] Updated SSL Support [IMP-519] Minimum TLS Support [IMP-472] TLS Server Name Indication [IMP-508] Standardized Log File Names [IMP-462] More Informative SSL Error Messages [00116516] [IMP-484] Renamed Keytab Property [IMP-520] Linux Installation Workflow Improvement [IMP-317] Support for Result Set Cache and Query Retry Resolved Issues: [00131357] [IMP-511] In some cases queries are not properly closed on the server, negatively impacting server resources. [IMP-486] In some cases, CAST AS VARCHAR does not function correctly. [00119275] [IMP-503] Connections from a machine with large amounts of RAM are slower than expected. [00132211] [IMP-523] Driver wide properties cannot be read from the .ini file. Getting Started with the Cloudera Driver Read the Cloudera ODBC 2.6.0 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

  We are pleased to announce the release of Impala JDBC v 2.6.4 .  The release has the following resolved issues:   Resolved Issues [00116966] [IMPJ-386] Documentation for the SocketTimeout configuration option is incorrect.   Breaking Changes The following are breaking changes to driver functionality. These changes may cause some workflows from earlier versions to fail.   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 Impala JDBC 2.6.4 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

  We are pleased to announce the release of Impala ODBC v2.5.44.  The release has the following fixes:   Resolved Issues in Impala ODBC 2.5.44 [00117025] [IMP-494] In some cases, when querying a table with a name that contains the suffix “_impala”, the driver truncates the suffix and then fails to query the table.    This issue has been resolved.   The driver no longer automatically truncates the “_impala” suffix, ensuring that the intended table name is used in the query. [IMP-504] The driver does not behave according to the Socket Timeout (or SocketTimeout) setting, and stops responding instead of returning an error when the server takes too long to respond to a request.   This issue has been resolved. The driver now returns an error if the amount of time taken by the server to respond to a request exceeds the number of seconds specified by the Socket Timeout or (SocketTimeout) setting.    Getting Started with the Cloudera Driver Read the Cloudera ODBC 2.5.44 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

  We are pleased to announce the release of Impala ODBC v2.5.43.  The release has the following fixes:   Resolved Issues in Impala ODBC 2.5.43 [00116516] The driver does not use the keytab mapping files as specified in the UPN Keytab Mapping File configuration option. The driver cannot file ODBCMessages.xml files in folders with names that include Japanese characters. [00115866] The driver treats the string “NULL” as a null value. [00116560] The driver inserts explicit “CROSS JOIN” in some queries for Impala versions higher than 1.2.1 and lower than 2.1.0, resulting in some inefficient queries.   Getting Started with the Cloudera Driver Read the Cloudera ODBC 2.5.43 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

  Subject: [ANNOUNCE] New Hive JDBC Driver Released   We are pleased to announce the release of Hive JDBC v2.6.2. The release has the following resolved issue.   Resolved Issues The driver does not behave according to the SocketTimeout setting, and stops responding instead of returning an error when the server takes too long to respond to a request. This issue has been resolved. The driver now returns an error if the amount of time by the server to respond to a request exceeds the number of seconds specified by the SocketTimeout setting.   Getting Started with the Cloudera Driver Read the Cloudera JDBC 2.6.2 Driver for 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 of 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 Impala ODBC v2.5.42.  The release has the following fixes and enhancements: Enhancements and New Features in Impala ODBC 2.5.42 [00097802] Backward compatibility added for Database connection property. When configuring your connection on a non-Windows machine or through a connection string, you can now use either the Schema or Database connection property to specify the name of the database schema for the connection. Prior to this update, support for the Database connection property had been removed. Resolved Issues in Impala ODBC 2.5.42 [00097666] Driver returns incorrect error code for when the Impala session times out and the auto-reconnection feature is disabled. This issue has been resolved. Before, the driver incorrectly returned a generic error code (SQL state HY000). The driver now returns SQL state 08S01 instead. In some cases, the driver fails to authenticate the connection through Kerberos. In certain scenarios, during query execution the system message "Error creating temporary swap file name" may be displayed. Getting Started with the Cloudera Driver Read the Cloudera ODBC 2.5.42 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

We are pleased to announce the release of Impala JDBC v 2.5.45 .  The release has the following resolved issues:   Impala JDBC 2.5.45   Resolved Issues in Impala JDBC 2.5.45 [00115543] A string literal after a back-tick ( ` ) is treated as a comment. [00115424] When the driver attempts to connect to the server using Beeline, an error occurs on the server and an exception is logged by the driver. This issue has been resolved. Now, when connecting the server using Beeline, connection properties such as “driver” and “url” are no longer treated as configurations properties for the server, and the driver does not send SET queries to the server with these properties.   Getting Started with the Cloudera Driver Read the Cloudera Impala JDBC 2.5.45 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

We are pleased to announce the release of Impala JDBC v2.6.3.  The release has the following enhancements:   Impala JDBC 2.6.3   Enhancements and New Features in Impala JDBC 2.6.3 [IMPJ-380] The driver has been upgraded to use Apache ZooKeeper 3.4.11. [IMPJ-381] The driver package now includes the file third-party-license.txt. This text file contains the license for all third-party software used in the driver. The third-party license information is also available in the Installation and Configuration Guide.   Resolved Issues in Impala JDBC 2.6.3 [00115517] [IMPJ-353] When attempting to close a statement that is already closed, the driver logs an error   Breaking Changes The following are breaking changes to driver functionality. These changes may cause some workflows from earlier versions to fail.   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 Impala JDBC 2.6.3 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

We are pleased to announce the release of Hive JDBC v2.6.1  The release has the following enhancements and fixes:   Enhancements and New Features in Hive JDBC 2.6.1 Improved installation process: Third-party libraries are now bundled with the driver as a shaded jar file. Updated hive-services: The driver has been upgraded to use hive-service-2.0.1 with JDBC 4.1 and hive-service-1.1.1 for JDBC 4. Updated third-party libraries: The driver has been upgraded to use http-client 4.5.3, http-core 4.4.6, commons-codec 1.9, commons-logging 1.2, and Zookeeper 3.4.11.   Resolved Issues [00115543] A string literal after a back-tick ( ` ) is treated as a comment. [00115424] When the driver attempts to connect to the server using Beeline, an error occurs on the server and an exception is logged by the driver. This issue has been resolved. Now, when connecting to the server using Beeline, connection properties such as "driver" and "url" are no longer treated as configuration properties for the server, and the driver does not send SET queries to the server with these properties. [00114906] The driver removes query comments and hints when the UseNativeQuery property is set to 1.   Breaking Changes The following are breaking changes to driver functionality. These changes may cause some workflows from earlier versions of the driver to fail.   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 Hive JDBC 2.5.43 Driver for 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 of through our community forums. You can also file bugs through our external Jira projects on issues.cloudera.org . ... View more