Click Impala → Queries to view the list of queries. By default, queries that completed execution over the past 24 hours are displayed. You can filter by Database, State, User, and Query Type. Click the Table Setting icon to select the list of columns that can be displayed on the table. You can select the columns that you want to view on the Query page. Click Apply to apply your changes.
The following metrics are displayed for each query.
|Query ID||The ID of the query.|
|Database||The database on which the query was run.|
|Resource Pool||The name of the resource pool used by the Query.|
|Duration||The total time taken by the query to run.|
|Variance||Variance indicates if a job is slower than previous runs. It is calculated as (avgValue - currentValue)/stdDeviation.|
|State||The state of the query, whether Running, Succeeded, Exception, or Finished. Cick the Log button to view the log details of the query|
|User||The user that ran the query.|
|Query Type||The type of the query, whether DDL, DML, or Query.|
|Coordinator||The name of coordinator node used by the query.|
|# of Rows||The number of rows produced by the query.|
|Thread CPU Time||The sum of the CPU time used by all threads of the query.|
|Per Node Peak Memory Usage||The peak memory usage per node.|
|HDFS Aggr Read Memory||The sum of HDFS bytes read from memory by the query.|
|Start Time||The date and time at which the query started running.|
|Completion Time||The date and time at which the query completed.|
You can view the incidents that were raised for the queries in the Incidents panel.
Select an incident group to filter the queries for which the incident applies.
Click View Incident to view all the incidents of a particular type in the Incidents side panel. Click an incident in the Incident panel to view its details.
Advanced Search Options
The search field in the Impala Queries Page supports Influx-like query statements. For example, if you want to search for a query, use the format parametername:value. However, you need to know the full name of the parameter to be able to use it. For example, the name of the parameter visible in the UI is User. However, internally, the parameter name is effective_user. Hence, if you want to search for queries with User = Mark, you need to type effective_user:Mark.