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 server. 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 the 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