You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Michael Smith (Jira)" <ji...@apache.org> on 2024/04/22 18:55:00 UTC
[jira] [Assigned] (IMPALA-13027) Directly create exec request for query log inserts
[ https://issues.apache.org/jira/browse/IMPALA-13027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Smith reassigned IMPALA-13027:
--------------------------------------
Assignee: Jason Fehr
> Directly create exec request for query log inserts
> --------------------------------------------------
>
> Key: IMPALA-13027
> URL: https://issues.apache.org/jira/browse/IMPALA-13027
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Michael Smith
> Assignee: Jason Fehr
> Priority: Major
>
> Inserts into {{sys.impala_query_log}} can be large, as they include the query profile and currently 49 columns for each query. Right now inserts are executed via an SQL statement, which needs to be parsed by Impala's Frontend. This can take a non-trivial amount of time - on the order of seconds - when reaching the query queue limit (1000s of queries), and also require increasing the {{statement_expression_limit}} above 250k.
> We could improve this by directly constructing the TExecRequest for the insert in InternalServer (likely via a new function API). This would also let us avoid needing to escape strings in the SQL statement by directly constructing the relevant type objects.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org