Created on 01-24-2019 01:56 PM - edited 09-16-2022 07:05 AM
Is there any examples available for impyla for how to connect to a kerberos cluster. the config in impala says ldap and I am not able to connect. Tried various combinations, various combinations of thrift/thrift-sasl versions and various versions of impyla as well.
But is there any documentation of examples available to look at what the connection properties are and if it works.
We have a kerborized cluster and it totally stops users from using it.
TTransportException: TTransportException(type=1, message="Could not start SASL: b'Error in sasl_client_start (-4) SASL(-4): no mechanism available: No worthy mechs found'")
This is the latest error where as all the options are available on the cluster.
Created 01-24-2019 07:30 PM
Created 01-25-2019 11:11 AM
from impala.dbapi import connect
from impala.util import as_pandas
conn = connect(host=kerurl, port=21050, auth_mechanism='GSSAPI')
cursor = conn.cursor()
This is the basic code we are trying, but the biggest challenge is kind of the old DLL hell, where there is not a right combination of the libraries..
impyla 14.1
thrift 0.3.0
thrift_sasl 0.11.0
gives different errors
AttributeError: 'TSocket' object has no attribute 'isOpen'
Where as the
impyla 13.8
thrift 0.2.1
thrift_sasl 0.9.3
gives
TTransportException: TTransportException(type=1, message="Could not start SASL: b'Error in sasl_client_start (-4) SASL(-4): no mechanism available: No worthy mechs found'")
Where as all underlying mechanisms are available.
Do you know of a good combination?
Created 04-24-2019 09:01 AM
Hi,
I have the same issue when connecting using:
* LDAP (username and password)
* SASL
* impyla
Can anyone help us to solve the issue?
Thanks
Rob
Created 08-27-2019 06:56 AM
We face the same problem on Windows OS. Which OS do you use?
Created on 09-05-2019 07:03 AM - edited 09-05-2019 07:04 AM
Having what appears to be exactly the same problem, on Windows 10 Enterprise.
impyla==0.15.0
thrift==0.11.0
thrift-sasl==0.3.0
But in thrift/transport/TSocket.py there absolutely is an isOpen() method. Not an attribute, but the way it is used in the code as pointed out by the error looks correct.
Created 09-05-2019 07:19 AM
Found this fix: https://github.com/cloudera/thrift_sasl/commit/d105152438ff78c2b1c041c79d1bcce25a760bb2
Unfortunately it throws other errors down the line. There seem to be a series of bugs in thrift_sasl.