[
https://issues.apache.org/jira/browse/SPARK-59689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matvei Zamiatin updated SPARK-59689:
------------------------------------
Component/s: SQL
(was: Spark Core)
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
