Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Impala unsupported set commands

avatar

Hi,

 I noticed that SET queries generated by a third party app on the Impala cluster are constantly failing. 

One example:

 

SET AllowSelfSignedCert=1

 

impala_set_fail.PNG

 

Is this something related to the Impala JDBC driver or are these coming from the application using this JDBC?

Can I somehow turn off this annoying SET command?

Thanks

 

Version: CDH5.15, Impala using TLS

 

1 ACCEPTED SOLUTION

avatar
It might be an application incorrectly trying to set the SIMBA driver option by SQL (which won't work). AFAIK the Simba JDBC driver won't do this itself.

View solution in original post

3 REPLIES 3

avatar
It might be an application incorrectly trying to set the SIMBA driver option by SQL (which won't work). AFAIK the Simba JDBC driver won't do this itself.

avatar
Master Collaborator

@Tomas79 Does your 3rd party support running 2 commands or SQL in the same file/document?

avatar

I have figured out that this is coming from the third party tool, so it has nothing to do with the Simba driver. 

Thanks