gatorsmile commented on a change in pull request #30808:
URL: https://github.com/apache/spark/pull/30808#discussion_r544774803



##########
File path: 
sql/core/src/main/scala/org/apache/spark/sql/SparkSessionExtensions.scala
##########
@@ -200,19 +200,20 @@ class SparkSessionExtensions {
     optimizerRules += builder
   }
 
-  private[this] val dataSourceRewriteRules = mutable.Buffer.empty[RuleBuilder]
+  private[this] val postOperatorOptimizationRules = 
mutable.Buffer.empty[RuleBuilder]
 
-  private[sql] def buildDataSourceRewriteRules(session: SparkSession): 
Seq[Rule[LogicalPlan]] = {
-    dataSourceRewriteRules.map(_.apply(session)).toSeq
+  private[sql] def buildPostOperatorOptimizationRules(
+      session: SparkSession): Seq[Rule[LogicalPlan]] = {
+    postOperatorOptimizationRules.map(_.apply(session)).toSeq
   }
 
   /**
-   * Inject an optimizer `Rule` builder that rewrites data source plans into 
the [[SparkSession]].
+   * Inject an optimizer `Rule` builder that rewrites logical plans into the 
[[SparkSession]].
    * The injected rules will be executed after the operator optimization batch 
and before rules
    * that depend on stats.
    */
-  def injectDataSourceRewriteRule(builder: RuleBuilder): Unit = {
-    dataSourceRewriteRules += builder
+  def injectPostOperatorOptimizationRule(builder: RuleBuilder): Unit = {

Review comment:
       To be honest, I do not like this name. Our catalyst is designed as a 
query compiler. There does not exist a concept in a query compiler called "Post 
Operator Optimization". If you talk about this extension point in a Database 
class, no one understands what it means from the name. 
   
   My point is still the same. Here, we are adding the extension point for 
advanced users to add the rules between the rule-based optimizer (RBO) rules 
and the cost-based optimizer (CBO) rules. 




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



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

Reply via email to