I’m getting the below error. I’m using the hive connector node to connect to processdatalake, one of my collogues has set up their connection the same way without issue. Not sure where to start in order to troubleshoot this error, any direction would be helpful.
ERROR DB Query Reader 0:16 Execute failed: org.apache.hive.service.cli.HiveSQLException: Error while processing statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask
at java.security.AccessController.doPrivileged(Native Method)
Hi @tkelhamMIL and welcome to the Knime Community.
It’s a bit hard to troubleshoot this without knowing what was done and how the workflow looks like.
May be we can start with 3 things to look at:
- What is the query that you are running?
- Was your connection still alive when you executed your query?
- Does the user you are using have the proper access?
I think all of the 3 above can be tested a once:
- Create a test workflow (new workflow file, or somewhere in your current workflow) with only the connector and the query reader/executor.
- Once the 2 nodes are ready, that is user is configured for the connector, and test query is ready for the query reader/executor, execute the query reader/executor node. It will automatically run the first node, that is the connector node, and make sure the query is run right after the connection is established.
This will make sure that the connection has not timed out, and will test if the user has proper access.
Hi @bruno29a the workflow is set up with a credentials node (yes, I have proper access and get a green stoplight. The query runs correctly when in datalake) , then there is a Hive connector node which also connects (green stoplight) which is then connected to the DB query reader which is where the error occurs when trying to run the query.
the query being run is rather simple
the query does not run even when trying to “evaluate” the same error is returned
Hi @tkelhamMIL and welcome to the KNIME Community,
This might happen if Hive can’t launch the container on your cluster and might have many reasons. Not sure what cluster you are running but having a look in the YARN logs of the container launched by Hive usually brings up more details about the error.
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.