Impala Queries
You can view information about the Impala queries that have run in your cluster during a selected time period. You can filter the queries using a simple filtering language.
You can configure whether admin and non-admin users can view all queries, only that user's queries, or no queries. See Configuring Query Visibility.

-
The Impala query monitoring feature requires Cloudera Impala 1.0.1 and higher.
-
Query information is stored in-memory in a ring buffer. This has two consequences: if you restart Service Monitor, all queries are lost and older queries eventually will be dropped. See Configuring Impala Query Store and Runtime Profile Maximum Size.
Queries List
Queries are ordered with the most recent at the top.
In each query summary, the query string is truncated if it is too long to display. To display the entire string, hover over a query. The query entry will expand to display the entire query string. To collapse the query display, move the mouse cursor.
To display information about query predicates and possible values, hover
over a field in a query. For example:

- The query is very simple and doesn't have interesting details.
- The query profile storage wasn't large enough.
To cancel a query labeled , click
. Only administrator can
cancel queries and canceling a query creates an audit event. Once the page is refreshed, a
label will replace the
label.
You can configure Cloudera Manager to display queries for all users, the queries generated by logged in user, or no queries. See Configuring Impala Query Results.
Filtering Queries
You filter queries by selecting a time range and specifying a filter expression.
You can use the Time Range Selector or
a time range link () to set the
time range for your search. (See Selecting a Time Range for details).
Constructing and Running a Filter
- Do one of the following:
- Click the
to the right of the Search button (
) to display a list of sample and recently used filters, and select a filter. When a filter sample is selected, the query filter text will be shown in the search box.
- Start typing or press Spacebar in the Search text box.
As you type, filter predicates matching the letter you type display. If you press
Spacebar, standard
filter predicates display. These suggestions are part of typeahead, which helps
build valid queries. For information about the predicate to use and supported
values for each field, hover over the field in an existing query.
- Select a predicate. Press Spacebar to display a list of applicable operators.
- Select an operator. Press Spacebar to display a list of application values.
- Click the
- Press Enter or click
. The Queries list displays the queries that match the specified filter.
Filter Expressions
Filter expressions specify which queries should be displayed when you run the filter. Filter expressions are made of three parts:
- Filter predicate - a property of the query. Cloudera Manager supports many filter predicates.
- Operator - the type of comparison between the query property and the property value. Cloudera Manager supports the standard comparator operators: =, !=, >, <, >=, <=, as well as RLIKE which does regular expression matching. Some operators are only applicable to certain filter predicates. For example, you can't use the > operator to compare the user predicate with the value root.
- Filter value - a value of the property. The value depends on the type of filter predicate. For some filter predicates, such as rowsProduced, specify numeric values; for other filter predicates, such as executing which take the Boolean values, specify either true or false. When specifying a string value, enclose the value in double quotes. For example, fileFormats = ".TEXT.*".
You can combine filter expressions using logical operators. For example, if you wanted to find all the queries issued by the root user that produced over 100 rows, use the filter:
user = "root" AND rowsProduced > 100
To find all the executing queries by Jack or Jill, use the filter:
executing = true AND (user = "Jack" OR user = "Jill")
Examples
Consider the following filter expressions: user = "root", rowsProduced > 0, fileFormats RLIKE ".TEXT.*", and executing = true. In the examples:
- The filter predicates are user, rowsProduced, fileFormats, and executing.
- The operators are =, >, and RLIKE.
- The filter values are root, 0, .TEXT.*, and true.