Created 10-19-2022 10:13 AM
When I attempt to' join' tables or even use 'group by', I get the following error:
Hortonworks Hive DSN -- [Hortonworks][Hardy] (35) Error from server: error code: '1' error message: 'Error while processing statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.tez.TezTask'.(HY000,35)
Yet, I am able to do a simple 'select-from-where' query with no problem.
I am using the IDE Rapid SQL.
Any idea of what is going on?
Created 09-04-2024 05:35 AM
If setting the proper queue name resolves the problem, it is possible that the query may have been submitted in the default queue, where it competes for resources with other queries and fails due to a timeout error
Created 09-30-2023 11:36 AM
It seems that the failure occurred within the Tez job's child tasks. To identify the root cause, please share the YARN logs of the failed application
Created 10-03-2023 02:02 PM
@hughes87 Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. If you are still experiencing the issue, can you provide the information @ggangadharan has requested? Thanks.
Regards,
Diana Torres,Created 08-30-2024 02:55 AM
Hello, have you manage to resolve your problem?
Cause I have the same. Via ODBC Simple Select works just fine, but something more complicated like nested SQL, PARTITION etc drop the same error.
But the same SQL running perfect without errors in Hue.
Thanks.
Created 09-02-2024 10:22 PM
Since the failure occurred within the Tez job's child tasks, please share the yarn log or complete Stacktrace from one of the failed child task attempts. This will help us identify the root cause of the failure and provide appropriate recommendations to resolve the problem.
Created 09-04-2024 04:46 AM
Hello ggangadharan, want to share my solution. After adding correct tez.queue.name prod value in ODBC advanced server connection options - everything started working like a charm.
Created 09-04-2024 05:35 AM
If setting the proper queue name resolves the problem, it is possible that the query may have been submitted in the default queue, where it competes for resources with other queries and fails due to a timeout error