[
https://issues.apache.org/jira/browse/IMPALA-12426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832509#comment-17832509
]
ASF subversion and git services commented on IMPALA-12426:
----------------------------------------------------------
Commit f55077007bf68e6cbeaa15cf270c333af847a1f1 in impala's branch
refs/heads/master from jasonmfehr
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=f55077007 ]
IMPALA-12426: Switches the duration fields to be stored in decimal seconds.
The original implementation of the completed queries table
stored durations in integer nanoseconds. This change
modifies the duration fields to be stored as seconds with
up to three digits of millisecond precision.
Also reduces the default max number of queued queries to a
number that will not consume as much memory.
Existing sys.impala_query_log tables will need to be
dropped.
Testing was accomplished by modifying the python custom
cluster tests.
Change-Id: I842951a132b7b8eadccb09a3674f4c34ac42ff1b
Reviewed-on: http://gerrit.cloudera.org:8080/21203
Reviewed-by: Michael Smith <michael.sm...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
> 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: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
