[
https://issues.apache.org/jira/browse/SPARK-59741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matvei Zamiatin updated SPARK-59741:
------------------------------------
Description:
CALL invokes a stored procedure. Currently the analyzer rule that resolves CALL
also invokes the procedure as a side effect — folding its arguments, running
it, and replacing the Call with its result — so the procedure executes during
analysis. Any path that only needs the schema (most notably a Spark Connect
schema-only analyze request) runs the procedure too.
Analysis should only resolve and bind the CALL, not invoke the procedure.
Invocation should happen at the normal execution phase, via a physical operator
that calls the procedure lazily and exactly once, the same way every other
command runs.
was:Same motivation as for https://issues.apache.org/jira/browse/SPARK-59689.
> Run CALL at execution time instead of during analysis
> -----------------------------------------------------
>
> Key: SPARK-59741
> URL: https://issues.apache.org/jira/browse/SPARK-59741
> Project: Spark
> Issue Type: Task
> Components: SQL
> Affects Versions: 4.4.0
> Reporter: Matvei Zamiatin
> Priority: Major
> Labels: pull-request-available
>
> CALL invokes a stored procedure. Currently the analyzer rule that resolves
> CALL also invokes the procedure as a side effect — folding its arguments,
> running it, and replacing the Call with its result — so the procedure
> executes during analysis. Any path that only needs the schema (most notably a
> Spark Connect schema-only analyze request) runs the procedure too.
> Analysis should only resolve and bind the CALL, not invoke the procedure.
> Invocation should happen at the normal execution phase, via a physical
> operator that calls the procedure lazily and exactly once, the same way every
> other command runs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
