[jira] [Resolved] (IMPALA-9774) impala-shell regression when connecting to cluster with SSL enabled

["Michael Smith (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-9774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Smith resolved IMPALA-9774.
-----------------------------------
    Fix Version/s: Impala 4.0.0
       Resolution: Fixed

I believe this is fixed since sasl was upgraded to 0.2.1.

> impala-shell regression when connecting to cluster with SSL enabled
> -------------------------------------------------------------------
>
>                 Key: IMPALA-9774
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9774
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Clients
>            Reporter: Tim Armstrong
>            Priority: Major
>             Fix For: Impala 4.0.0
>
>
> {noformat}
> $ impala-shell -i xxxxxxxxxxx.vpc.cloudera.com -d default -k --ssl --ca_cert /xxxxxx.pem
> Starting Impala Shell with Kerberos authentication using Python 2.7.5
> Using service name 'impala'
> SSL is enabled
> No handlers could be found for logger "thrift.transport.sslcompat"
> Error connecting: NotImplementedError, Wrong number of arguments for overloaded function 'Client_setAttr'.
>   Possible C/C++ prototypes are:
>     setAttr(saslwrapper::Client *,std::string const &,std::string const &)
>     setAttr(saslwrapper::Client *,std::string const &,uint32_t)
> {noformat}
> This was caused by the unicode changes in "IMPALA-3343, IMPALA-9489: Make impala-shell compatible with python 3" - in some places a unicode string gets passed into the sasl library, and the older version of the library can't handle it. The SASL upgrade - IMPALA-9719 - fixes it.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org