Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
MikePheysey
Partner - Contributor
Partner - Contributor

Spark ODBC Connector connects but does not identify my databases

Hello all,

On QS Nov 2021 I am trying to connect to a Spark Thrift server ( Spark 3.1.1 ) running in Kubernetes.  I am able to test and establish a SASL Username only connection using both the Apache Spark ODBC Connector and the Databricks Connector, however when I access the saved connection in the Data Load Editor and open the Select Data to load dialog, the database I specified in the connection does not show up in the drop down of owners, and none of my tables are visible.

When I open the Select Data To Load, I see an exception in the thrift server logs : '[WARN ] got exception trying to get groups for user <my_user>: id '<my_user>': no such user id: '<my_user>': no such user.

I have installed the Simba Spark ODBC driver separately and configured a System ODBC DSN using the same username, host, port and authentication options and my Qlik ODBC data connection using this DSN works just fine.  

Has anyone encountered something similar and found a solution?  

Labels (2)
1 Solution

Accepted Solutions
Francisco_Fernandez

Hello @MikePheysey ,

Yes, I would suggest that you open a case since we would need to reproduce this.

 

Best regards,

Francisco

View solution in original post

3 Replies
Francisco_Fernandez

Hi @MikePheysey ,

Could you please provide a screenshot of the error message?

MikePheysey
Partner - Contributor
Partner - Contributor
Author

Hello @Francisco_Fernandez .  Here is a screen shot of the thrift logs at the time I attempted to view tables using the built in Apache Spark connector.  I have a lot more shots and logs as I was getting ready to open a support issue before trying the community first 🙂

Spark_Thrift_Logs_ODBC_Connection.png

Francisco_Fernandez

Hello @MikePheysey ,

Yes, I would suggest that you open a case since we would need to reproduce this.

 

Best regards,

Francisco