Check beeline console output and HS2 logs to identify where it gets stuck and act accordingly.  ... View more

The error message Invalid SessionHandle: SessionHandle commonly occurs in Hive when there is an issue with the session handle being used. A session handle in Hive is a unique identifier for a session created when a user connects to Hive, used to maintain the state and context of the session. One possible scenario for this error is when a table contains a large number of records and the cluster has multiple HS2 instances. If Knox is used to connect to Hive, Knox might connect to one HS2 and run a query. However, due to the large number of records, the query takes longer to process. If the connection times out from Knox's end and reconnects to another HS2, the query might fail with the "Invalid SessionHandle" error. To investigate this scenario, it is recommended to check the HS2 logs and Knox logs. Additionally, to determine why the query is running long, checking the HS2 and appLogs for any yarn job initiated by HS2 can provide further insights. ... View more

First of all , It is not recommended to use the same location for both internal and external tables. Internal tables in Hive are native tables that are fully controlled by Hive itself. External tables, on the other hand, can be accessed by other components such as Spark, Impala, and File system operations,.....etc. Since External tables are used by other components, their corresponding locations need to be relied upon. To read the files and obtain the count, Hive launches a MapReduce job for external tables. It is recommended to use Managed tables if other components are not utilizing the corresponding table.  ... View more

From the attached console output noticed AM failed to submit the DAG. ERROR : Failed to execute tez graph. org.apache.tez.dag.api.SessionNotRunning: TezSession has already shutdown. Application application_1730584072947_0051 failed 1 times (global limit =2; local limit is =1) due to AM Container for appattempt_1730584072947_0051_000001 exited with exitCode: 1  Please check the appLogs application_1730584072947_0051 to identify the root cause of the failure.  ... View more

If you suspect that TEZ-4032 is the cause, consider upgrading your cluster to CDP 7 and testing it again, as it has been backported in CDP 7. ... View more

Ideally below should work.  use default;show tables; Please check HiveServer2, HMS logs and share the stack-trace.  To identify the RootCause.  ... View more

The query seems to be failing during the compilation phase, indicating a possible issue with its syntax. Error: Error while compiling statement: FAILED: ParseException line 1:11 missing EOF at ';' near 'default' (state=42000,code=40000) It is important to validate the SQL syntax of the query to identify any potential syntax errors that may be causing the problem. Another point to consider is ensuring that the column names in the query match with those in the source and target tables, as any mismatch can lead to errors. ... View more