When I tried to write output to hive using DB Loader node, sometimes it gives an error that the output table doesn’t exist in hive workspace, where that table actually exists. If I reset the connect and rerun the node, sometimes it fixes the issue, but sometimes it still has the same error. Does anyone know what might be the cause of this issue and how can I fix it?
this is related to a timeout when reading the metadata during node configuration. This only happens if Hive is not responding within the set timeout. To disable the timeout you can deselect the “Retrieve in configure” option of the Metadata section of the Advanced settings tab. We have a ticket for making this clearer in the node as well.
I am still having the same issue after changing the settings.
One of my hive connector is linked to two db loader nodes, one of them ran successfully and the other failed.
Is there anything else I could do to solve this issue?
@karen2180 could you give us more context about your settings? Which version of Hive are you using, how do you handle table statistics (if at all). Do you also use Impala? Is the table newly being created in the KNIME workflow or is it there all along?
How does your DB loader construct look? With Hive if you want to upload a file you would have to first create it and then upload the data to an existing file. Maybe you could provide us with a screenshot, and maybe also the Log files.
My KNIME version is 4.1.1, and we are using CDP Hive. I use flow variables to control both the schema, table name, and the directory, shown as below.
The table has been created for a while. The db loader node works most of the time if I run the workflow locally, but only works occasionally if I run it on the server.
For starters I would recommend to load the data into a temporary table on the cluster and then insert it into the final table. And do you have some sort of logfile or error message
The only error message I got is “table doesn’t exist”.
In order for us to be of any help some more details might be needed.
Were you able to try and first load the data into a temporary file and then INSERT it into a final table.
Could you set the log level to debug and provide us with the logfile? Best to first delete the existing one and start from when the problem occurs.
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.