You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Uroš Bojanić (Jira)" <ji...@apache.org> on 2026/09/23 20:51:00 UTC

[jira] [Assigned] (SPARK-59689) Run EXECUTE IMMEDIATE commands at execution time instead of during analysis

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

Uroš Bojanić reassigned SPARK-59689:
------------------------------------

    Assignee: Matvei Zamiatin

> Run EXECUTE IMMEDIATE commands at execution time instead of during analysis
> ---------------------------------------------------------------------------
>
>                 Key: SPARK-59689
>                 URL: https://issues.apache.org/jira/browse/SPARK-59689
>             Project: Spark
>          Issue Type: Task
>          Components: SQL
>    Affects Versions: 4.4.0
>            Reporter: Matvei Zamiatin
>            Assignee: Matvei Zamiatin
>            Priority: Major
>              Labels: pull-request-available
>
> EXECUTE IMMEDIATE resolves a dynamic SQL string and runs it. Until now, when that string was a command (e.g. CREATE VIEW, SET, INSERT), the analyzer rule that resolves EXECUTE IMMEDIATE also ran the command as a side effect - so the command executed during analysis.
> This task intended to make the analyzer only parse and analyze the dynamic SQL. A command payload is wrapped in a new ExecuteImmediateCommand logical node and executed later at the normal execution phase (via ExecuteImmediateExec), the same way every other command runs. Queries and INTO are unchanged: a query is spliced and runs lazily, INTO becomes a SetVariable.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org