[
https://issues.apache.org/jira/browse/IMPALA-12426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795553#comment-17795553
]
ASF subversion and git services commented on IMPALA-12426:
----------------------------------------------------------
Commit 408c606dd9b891b3abc7f5ce95c95a92334abb8b in impala's branch
refs/heads/master from jasonmfehr
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=408c606dd ]
IMPALA-12426: Adds the backend InternalServer class.
This class is intended for use by backend code within an
Impala coordinator to submit queries to itself. It works
by directly calling backend methods on the ImpalaServer
instance. By directly calling these methods, user
authentication is bypassed. However, authorization (such as
Ranger rules) is applied. Additionally, overhead associated
with protocol management (Beeswax and HS2) is eliminated.
This code is not yet in use.
Testing consists of a new type of backend ctest tests.
These tests join an existing, running Impala cluster in
order to execute queries, inserts, dmls, and ddls using
the new InternalServer class. Test cases ensure multiple
sql statement can be run in the same session and also in
separate sessions. Negative testing also ensures timeouts
and invalid query options are handled correctly.
Change-Id: I27686aa563fac87429657e4980b29b0da91eb9e1
Reviewed-on: http://gerrit.cloudera.org:8080/20524
Reviewed-by: Impala Public Jenkins <[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: Improvement
> 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.
> Design details:
> # New Coordinator Startup Flags:
> ## store_query_history – string, value of "impala" stores the query history
> table as an Iceberg table, allows for future expansion to using Kudu as the
> table storage engine
> ## query_history_table_name – string, name of the table where query history
> will be stored, can be fully qualified with a database name (e.g.
> "mydb.my_table") or can be just the table name (e.g. "my_table") in which
> case the table will be stored in the "information" database, defaults to
> "information.query_history"
> ## query_history_write_duration – number, seconds to wait before inserting
> completed queries into the query history table, allows for batching inserts
> to avoid lots of small files, value of 0 indicates immediate insert with no
> batching, default 300
> # Not all queries will be inserted in this table. Use/set/get queries as well
> as insert dmls to this table will not be inserted.
> # The query history table will include data from the query profile that
> describe the overall query (e.g. query_id, session_id, user, sql, coordinator
> name, start time, end time, etc)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
