Support Questions

Find answers, ask questions, and share your expertise

Hortonworks Hive 35 Error

avatar
New Contributor

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?

1 ACCEPTED SOLUTION

avatar
Master Collaborator

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

View solution in original post

6 REPLIES 6

avatar
Master Collaborator

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

avatar
Community Manager

@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,
Community Moderator


Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community:

avatar
New Contributor

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.

avatar
Master Collaborator

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.

avatar
New Contributor

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.

avatar
Master Collaborator

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