This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I have a quite long workflow in our private gallery which runs perfectly well on small datasets (less than 1 hour of run).
It retrieves data from an IBM DB2 server, stores it in Impala/HDFS, does some processing and then final result stored in Impala again.
When the same workflow is run for larger datasets (6-10 hours of processing), it fails while creating some of the impala tables with the following error message:
Executing PreSQL: "CREATE TABLE ..." : [Cloudera][ODBC] (10000) General error: Unexpected exception has been caught. (Tool Id: 416)
Have you experienced such a behavior before ?
Having tried a number of remedial actions, like optimizing the size of the datasets, recreating the DSN used, upgrading the Impala ODBC driver to a recent one, recreating new in-DB connections, etc.. I still have the same message.
As I am using Kerberos with SSPI, the only track I believe can explain this is the one of Kerberos ticket expiry given the lenght of the workflow execution.
Is there any option to ascertain the Kerberos ticket obtained by Alteryx server remains valid even after 10 hours of run? If not, is there anyway to manually inquire for a ticket with a longer validity that Alteryx server would then use ?
Good guess mutama. I should probably try that. Unfortunately, I do not have admin rights to generate keytab file from Active Directory power shell or schedule a task on the server.
Workaround so far has been to load file via HDFS (regular alteryx output) and via SSH in the run command tool of Alteryx generate a json schema and a create a table attached to the HDFS. Much faster than writing impala directly from Alteryx.