Github user cloud-fan commented on a diff in the pull request:

    https://github.com/apache/spark/pull/15945#discussion_r95782620
  
    --- Diff: 
sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -90,18 +92,27 @@ class QueryExecution(val sparkSession: SparkSession, 
val logical: LogicalPlan) {
        * Prepares a planned [[SparkPlan]] for execution by inserting shuffle 
operations and internal
        * row format conversions as needed.
        */
    -  protected def prepareForExecution(plan: SparkPlan): SparkPlan = {
    -    preparations.foldLeft(plan) { case (sp, rule) => rule.apply(sp) }
    -  }
    +  protected def prepareForExecution(plan: SparkPlan): SparkPlan = 
execute(plan)
    +
    +  private val fixedPoint = 
FixedPoint(sparkSession.sessionState.conf.optimizerMaxIterations)
     
       /** A sequence of rules that will be applied in order to the physical 
plan before execution. */
    -  protected def preparations: Seq[Rule[SparkPlan]] = Seq(
    -    python.ExtractPythonUDFs,
    -    PlanSubqueries(sparkSession),
    -    EnsureRequirements(sparkSession.sessionState.conf),
    -    CollapseCodegenStages(sparkSession.sessionState.conf),
    -    ReuseExchange(sparkSession.sessionState.conf),
    -    ReuseSubquery(sparkSession.sessionState.conf))
    +  override protected def batches: Seq[Batch] = Seq(
    --- End diff --
    
    How about we add a `PhysicalOptimizer` to do these things? then we can 
simply write `lazy val executedPlan: SparkPlan = 
physicalOptimizer.execute(sparkPlan))` instead of `lazy val executedPlan: 
SparkPlan = prepareForExecution(sparkPlan)`


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to