Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

H190 Unable to fetch results metadata error.need help

avatar
Rising Star

We are getting the following error in Hive query editor.This error occurs inconsistently.Select queries are working fine.We are using Ambari 2.2.2.2.

1 ACCEPTED SOLUTION

avatar
Super Guru

@Shihab

Hive view calls GetResultSetMetadata without verifying query completion with GetOperationStatus. This results in an error status from hive server. This is https://issues.apache.org/jira/browse/AMBARI-13575 bug that supposed to be fixed in 2.2.0. However, you may encounter a variation of the same issue. There is no issue to track it. You should login to https://issues.apache.org/jira/browse/AMBARI-19313?jql=project%20%3D%20AMBARI and submit the issue with proper documentation.

If you are still on Ambari 2.2.2.2, try to upgrade to a more recent version. I have seen the error you describe in 2.2.x versions, but I haven't seen it on 2.4.x. I recall seeing some similar issues with 2.3.x as well.

View solution in original post

2 REPLIES 2

avatar

@Shihab

Can you please check and Hive metastore? Please provide metastore logs for details understanding.

avatar
Super Guru

@Shihab

Hive view calls GetResultSetMetadata without verifying query completion with GetOperationStatus. This results in an error status from hive server. This is https://issues.apache.org/jira/browse/AMBARI-13575 bug that supposed to be fixed in 2.2.0. However, you may encounter a variation of the same issue. There is no issue to track it. You should login to https://issues.apache.org/jira/browse/AMBARI-19313?jql=project%20%3D%20AMBARI and submit the issue with proper documentation.

If you are still on Ambari 2.2.2.2, try to upgrade to a more recent version. I have seen the error you describe in 2.2.x versions, but I haven't seen it on 2.4.x. I recall seeing some similar issues with 2.3.x as well.