Cloudera ODBC Driver for Impala

Transcription

1 Cloudera ODBC Driver for Impala Released These release notes provide details of enhancements, features, and known issues in Cloudera ODBC Driver for Impala , as well as the version history. Support for CDH 5.12 The driver now supports CDH versions 5.0 through The following issues have been resolved in Cloudera ODBC Driver for Impala [ ] If a query fails due to "Memory Limit Exceeded", the query is not closed. [ ] CHAR field length reports incorrect values. Driver log file name does not include vendor. Version History Version Released Support for Impala 2.9 The driver now supports Impala versions through 2.9. [ ] Driver-wide configurations You can now set configuration options so that they apply to every connection that uses the driver. Before, most configuration options had to be set individually for each connection. 1

2 [ ] DelegationUIDCase renamed The DelegationUIDCase property has been renamed. It is now called DelegationUserIDCase. [ ] Automatic server SPN canonicalization The driver now automatically canonicalizes the server SPN when using Active Directory Kerberos. The following issues have been resolved in Cloudera ODBC Driver for Impala [ ] On macos, the driver sometimes terminates unexpectedly when authenticating the connection through Kerberos. [ ] Driver installation fails on Linux. This issue has been resolved. The issue occurred because the RPM file used an incorrect file path for the installation directory. [ ] If a query contains a scalar subquery, the driver returns an error and fails to execute the query. Version Released Restrict catalog functions to current schema If a schema is not specified for a catalog function, or if a schema is specified with the wildcard character %, you can choose to restrict the catalog function to the current schema. This may improve performance. To do this, select the Restrict Metadata with Current Schema GUI option, or set the CurrentSchemaRestrictedMetadata connection setting to 1. The following issues have been resolved in Cloudera ODBC Driver for Impala

3 [ ] The driver incorrectly adds a length to all the type name in CAST statements during query translation. In the driver log, the driver is reported as read-only, despite being read/write enabled. The driver does not correctly retrieve infinity value for FLOAT columns. The driver does not correctly retrieve NaN (Not a Number) value for FLOAT columns. Version Released [ ] Convert letter case of delegated user names You can now configure the driver to change the Delegation UID (or DelegationUID) value to all upper-case or all lower-case. To do this, set the DelegationUIDCase connection property. Version Released Specify asynchronous exec poll interval You can now specify the time in milliseconds between each poll that the driver makes for the query execution status. Specify the number of milliseconds in the Advanced Options dialog box in the Async Exec Poll Interval field, or in the AsyncExecPollInterval configuration option. Support for Impala 2.8 The driver now supports Impala versions through 2.8. Specify Kerberos host name canonicalization By default, if you specify a Kerberos realm, the Kerberos layer canonicalizes the host FQDN in the server s service principal name. You can disable this behavior 3

4 by disabling the Canonicalize Principal FQDN option, or by setting the ServicePrincipalCanonicalization connection property to 0. Configure SSL certificate revocation check You can now configure the driver to check whether a TLS/SSL certificate that is stored in the Windows Trust Store has been revoked. By default, the driver checks for revocation. To disable the revocation check, clear the Check Certificate Revocation check box, or set the CheckCertRevocation key to 0. Simplified MIT Kerberos configuration When using MIT Kerberos to access the Impala service from a Kerberos realm that is different than the Kerberos realm that the user belongs to, the user is no longer required to add the Impala service's network domain to the Kerberos realm mapping in the Kerberos configuration file on the client machine. Upgraded OpenSSL library The driver now uses OpenSSL Previously, the driver used OpenSSL 1.0.1l. The following issues were resolved in Cloudera ODBC Driver for Impala [92116] Conflicting information in documentation regarding CDH. [91995] Incorrect driver version verification instructions for macos in documentation. [92492] Segmentation fault in Driver Manager detection on Linux and Solaris Sparc platforms. Queries using DISTINCT run correct in HUE but not via ODBC. Driver converts COALESCE function to less efficient Impala CASE statement. When attempting to use the Windows trust store on Windows Server 2016, an access violation exception occurs. 4

5 Version Released [13858] Support added for Kerberos delegation You now have the option for the driver to forward the user credentials to the server when using Kerberos authentication. Support for Windows Trust Store You now have the option to use the CA certificates in the Windows Trust Store for server verification when using SSL. [13800] Auto Reconnect You can configure the driver to automatically attempt reconnection to the Impala server if communications are lost. [13996] Support for query, login, and connection timeout The driver now supports the following ODBC API calls: SQL_ATTR_CONNECTION_TIMEOUT SQL_ATTR_LOGIN_TIMEOUT SQL_ATTR_QUERY_TIMEOUT [14244] Optimization of metadata retrieval Driver performance during metadata retrieval has been optimized. The following issues were resolved in Cloudera ODBC Driver for Impala If a user attempted to connect without proper permissions to access the schema set in the connection string, the driver would fail to connect. The driver will now display a warning under these circumstances, and use the default schema. [13523] Specifying an alias for a column name in the SELECT list when SELECT DISTINCT is present and using that column name in the ORDER BY clause causes a system message to be displayed. 5

6 [13656] Driver returning incorrect order for character data types in the SQLGetTypeInfo result set under some circumstances. Version Released Support added for SQL_TSI_FRAC_SECOND precision The driver now supports queries that use the TIMESTAMPDIFF and TIMESTAMPADD scalar functions with the SQL_TSI_FRAC_SECOND precision. [13780] Support added for TLS versions up to 1.2 The driver can now connect to the database using TLS 1.2 or earlier. For detailed information about configuring TLS/SSL settings, see the Cloudera ODBC Driver for Impala Installation and Configuration Guide. The following issues were resolved in Cloudera ODBC Driver for Impala Driver returns non-selected columns specified in the ORDER BY clause. Syntax error when using parameters in case expressions, specifically in the ELSE and THEN clauses. Using alias for a column name in SELECT DISTINCT List does not resolve properly for the ORDER BY clause. [13794] When translating a CAST statement, the query translator removes the length from CHAR and VARCHAR data. [13655] If a statement contains a CASE expression that uses THEN or ELSE as well as a parameter, and the statement also contains a GROUP BY clause that uses the same column as the CASE expression, then the driver returns a syntax error. 6

7 Version Released Support added for EXISTS syntax The driver now supports queries that use the EXISTS syntax. [12888] Additional SQLColumn optimization The following issues were resolved in Cloudera ODBC Driver for Impala [13202] Query fails if the column name contains a char from the Latin-1 Supplement char set. [13205] Warning dialog when non-admin user clicks OK on the DSN dialog should be suppressed. Driver reports statement length limit as 16K. Version Released Support added for Red Hat Enterprise Linux (RHEL) 7 and CentOS 7 You can now install and run the Linux version of the driver on machines that run RHEL 7 or CentOS 7. Improved implementation of SQLCancel The driver now implements industry-standard behavior for when SQLCancel is called while query results are being fetched. Optimized metadata retrieval The driver now retrieves schemas and table names using the SHOW TABLES query instead of the GetTables Thrift API call. 7

8 The following issues were resolved in Cloudera ODBC Driver for Impala The Use Only SSPI configuration option (the UseOnlySSPI property) does not work correctly. [12888] Driver does not push down restrictions for catalog functions (SQLTables and SQLColumns), in some cases causing a large number of GET_TABLES requests to occur. When connecting to Impala 1.1 and executing a query that contains a NULL literal in the SELECT list, the driver terminates unexpectedly. Version Released [12116] Advanced Kerberos authentication mechanism implemented The driver now supports Advanced Kerberos authentication, which allows concurrent connections within the same process to use different Kerberos user principals. For information about how to use this authentication mechanism, see the Cloudera ODBC Driver for Impala Installation and Configuration Guide. Updated handling of result set metadata The driver now reports result set columns as being updatable, improving compatibility with the DotNet Odbc library and OdbcDataAdapter. Support added for returning table and column remarks through catalog functions The driver is now able to return remarks from tables and columns through catalog functions. Note: Currently, due to a known issue in Impala, table remarks are returned as empty strings. When the GetTables Thrift client API is called, Impala returns empty strings for table remarks even if the table contains remarks. 8

9 Version Released Automatically configure driver manager settings On non-windows platforms, the DriverManagerEncoding and ODBCInst settings are now configured automatically based on the driver manager (iodbc or unixodbc) that is used. Updated driver logging options You can now specify the maximum size of each log file by using the "Max File Size" option (the LogFileSize key), and specify the maximum number of log files to keep by using the "Max Number Files" option (the LogFileCount key). Also, in the Logging Options dialog box for the Windows driver, you now have the option of browsing for the folder where you want to save log files instead of typing the path. 9

10 Contact Us If you are having difficulties using the driver, our Community Forum may have your solution. In addition to providing user to user support, our forums are a great place to share your questions, comments, and feature requests with us. If you are a Subscription customer you may also use the Cloudera Support Portal to search the Knowledge Base or file a Case. Important: To help us assist you, prior to contacting Cloudera Support please prepare a detailed summary of the client and server environment including operating system version, patch level, and configuration. 10