Hi SHoffmann,   given that my customer enjoys paid Cloudera support and I insisted on getting an answer to the problem on behalf of the customer the Cloudera support provided the following answer:   JDBC using authentication does not work for the Impala driver   There are two workarounds to this only: 1) install LDAP and Kerberos then the JDBC driver will start working 2) use AuthMech=0 (no authentication at all) If neither of the above is an option for you then you can use ODBC driver which supports plain user/pw authentication   Best regards jaro ... View more

Thank you very much, Tim and Ivan.   I have tested on customer system and with "set disable_codegen=1;" the query does NOT crash the whole impala cluster anymore.   I will inform the customer and provide  him with a link to this discussion ... View more

thank you, SparkeyG!   for the YARN environment snippet should I add the same string (PYSPARK_PYTHON)?   ... View more

Dear SparkeyG, pls would you elaborate on how to add the PYSPARK_PYTHON variable to YARN configuration snippet as per your suggestion? What format do I need to use for the snippet? Would you be so kind and post an example? Thank you jaro ... View more

Hello,   I would like to step into this discussion as well.   I cannot establish a connection to Impala (impalad version 2.3.0-cdh5.5.1 RELEASE) using the recommended JDBC drivers ("Cloudera_ImpalaJDBC4_2.5.5.1007.zip" - com.cloudera.impala.jdbc4.Driver).   Impala is configured to use Sentry for authorization and with the HDFS synchronization plugin activated, otherwise no LDAP and no Kerberos. User - Group mappings are provided by OS.   Used connection strings: jdbc:impala://:21050/;UID=;PWD=;AuthMech=3;auth=noSasl; and jdbc:impala://:21050/;UID=;PWD=;AuthMech=3; in both cases the client   The client never manages to connect to the Impala daemon and each connection attempt results in "Connection time out".   Tthe only successful connection is with this string: jdbc:impala://:21050;AuthMech=0; but this is not really useful because as anonymous / unauthorized user I have no privileges and the only db that can be accessed is "default" and no operation can be performed The documentation in "Cloudera - Simba JDBC Driver for Cloudera Impala Install Guide.pdf" is incomplete and contradictory (e.g.undocumented "auth" property, and in the newest version of the guide "Cloudera_ImpalaJDBC41_2.5.31.zip" there are confusing mentions of non-existing licence files "ClouderaClouderaImpalaJDBCDriver.lic")   Has anyone succeeded to connect to Impala with Sentry without LDAP/Kerberos?   I have also raised an official incident with Cloudera Services on behalf of my customer.   Thank you jaro ... View more

is the Cloudera Impala driver open-source? would you point me to its source code repository?   thank you jaro ... View more

version "Cloudera_ImpalaJDBC41_2.5.31.zip"   page 8:   "Before you can use the Cloudera JDBC Driver for Impala, you must place the ClouderaClouderaImpalaJDBCDriver.lic file in the same directory as the ImpalaJDBC3.jar, ImpalaJDBC4.jar, or ImpalaJDBC41.jar file." ... View more