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 "Arnab Karmakar (Jira)" <ji...@apache.org> on 2025/10/24 10:00:00 UTC

[jira] [Assigned] (IMPALA-13342) Query option to dump TExecRequest

     [ https://issues.apache.org/jira/browse/IMPALA-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arnab Karmakar reassigned IMPALA-13342:
---------------------------------------

    Assignee: Arnab Karmakar

> Query option to dump TExecRequest
> ---------------------------------
>
>                 Key: IMPALA-13342
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13342
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Backend, Frontend
>            Reporter: Quanlong Huang
>            Assignee: Arnab Karmakar
>            Priority: Major
>              Labels: ramp-up
>
> To investigate planner bugs like IMPALA-13274, it'd be helpful to check the TExecRequest of the query. However, enabling TRACE level logs of Frontend doesn't dump it. There is a flag, dump_exec_request_path, which will let coordinator dump the TExecRequest to files under the given folder. That's a startup flag that requires a restart and will dump TExecRequests for all queries.
> A query option that lets coordinator output the TExecRequest to the client without executing the query will be helpful. Note that the query might cause crash so we don't want it to be executed. Explaining the query will get a different TExecRequest.



--
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