You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2020/08/19 16:27:00 UTC
[jira] [Resolved] (SPARK-28863) Add an AlreadyPlanned logical node
that skips query planning
[ https://issues.apache.org/jira/browse/SPARK-28863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-28863.
---------------------------------
Fix Version/s: 3.1.0
3.0.1
Resolution: Fixed
Issue resolved by pull request 29469
[https://github.com/apache/spark/pull/29469]
> Add an AlreadyPlanned logical node that skips query planning
> ------------------------------------------------------------
>
> Key: SPARK-28863
> URL: https://issues.apache.org/jira/browse/SPARK-28863
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Burak Yavuz
> Assignee: Burak Yavuz
> Priority: Major
> Fix For: 3.0.1, 3.1.0
>
>
> With the DataSourceV2 write operations, we have a way to fallback to the V1 writer APIs using InsertableRelation.
> The gross part is that we're in physical land, but the InsertableRelation takes a logical plan, so we have to pass the logical plans to these physical nodes, and then potentially go through re-planning.
> A useful primitive could be specifying that a plan is ready for execution through a logical node AlreadyPlanned. This would wrap a physical plan, and then we can go straight to execution.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org