/clusters/{clusterName}/services/{serviceName}/impalaQueries
Mount Point: /api/v16/clusters/{clusterName}/services/{serviceName}/impalaQueries
GET
Returns a list of queries that satisfy the filter
Available since API v4.
Parameters
name | description | type | default |
---|---|---|---|
serviceName | The name of the service | path | |
filter | A filter to apply to the queries. A basic filter tests the value of an attribute and looks something like 'rowsFetched = 1' or 'user = root'. Multiple basic filters can be combined into a complex expression using standard and / or boolean logic and parenthesis. An example of a complex filter is: 'query_duration > 5s and (user = root or user = myUserName)'. An example of expected full query string in requested URL is: '?filter=(query_duration > 5s and (user = root or user = myUserName))'. | query | |
from | Start of the period to query in ISO 8601 format (defaults to 5 minutes before the 'to' time). | query | |
to | End of the period to query in ISO 8601 format (defaults to current time). | query | now |
limit |
The maximum number of queries to return. Queries will be
returned in the following order:
|
query | 100 |
offset | The offset to start returning queries from. This is useful for paging through lists of queries. Note that this has non-deterministic behavior if executing queries are included in the response because they can disappear from the list while paging. To exclude executing queries from the response and a 'executing = false' clause to your filter. | query | 0 |
serviceName | (no documentation provided) | path | |
clusterName | (no documentation provided) | path |
Response Body
element: | impalaQueryResponse |
A list of impala queries and warnings