[
https://issues.apache.org/jira/browse/IMPALA-12426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832327#comment-17832327
]
ASF subversion and git services commented on IMPALA-12426:
----------------------------------------------------------
Commit deee153c76d2856dd5405137f45fb47bc267f99b in impala's branch
refs/heads/master from jasonmfehr
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=deee153c7 ]
IMPALA-12426: Skip Inserting HS2 Operation Queries into the Completed Queries
Table
Prevents queries associated with HS2 metadata operations
from being written to the completed queries table. These
queries are represented by the TMetadataOpcode enum.
A Custom cluster test that makes an HS2 connection to
Impala and runs these operations has been added. This test
asserts that none of the operations have their queries
written to the completed queries table.
Change-Id: Ie19cf5953522fa85941e6c0b9c15a9c9ba9dc362
Reviewed-on: http://gerrit.cloudera.org:8080/21207
Reviewed-by: Michael Smith <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> SQL Interface to Completed Queries/DDLs/DMLs
> --------------------------------------------
>
> Key: IMPALA-12426
> URL: https://issues.apache.org/jira/browse/IMPALA-12426
> Project: IMPALA
> Issue Type: New Feature
> Components: Backend, be
> Reporter: Jason Fehr
> Assignee: Jason Fehr
> Priority: Major
> Labels: impala, workload-management
>
> Implement a way of querying (via SQL) information about completed
> queries/ddls/dmls. Adds coordinator startup flags for users to specify that
> Impala will track completed queries in an internal table.
> Impala will create and maintain an internal Iceberg table named
> "impala_query_log" in the "system database" that contains all completed
> queries. This table is automatically created at startup by each coordinator
> if it does not exist. Then, each completed query is queued in memory and
> flushed to the query history table either at a set interval (user specified
> number of minutes) or when a user specified number of completed queries are
> queued in memory. Partition this table by the hour of the query end time.
> Data in this table must match the corresponding data in the query profile.
> Develop automated testing that asserts this requirement is true.
> Don't write use, show, and set queries to this table.
> Add the following metrics to the "impala-server" metrics group:
> * Number of completed queries queued in memory waiting to be written to the
> table.
> * Number of completed queries successfully written to the table.
> * Number of attempts that failed to write completed queries to the table.
> * Number of times completed queries were written at the regularly scheduled
> time.
> * Number of times completed queries were written before the scheduled time
> because the max number of queued records was reached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
