You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by rxin <gi...@git.apache.org> on 2014/06/19 03:21:10 UTC

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

GitHub user rxin opened a pull request:

    https://github.com/apache/spark/pull/1123

    [SPARK-2187] Explain should not run the optimizer twice.

    @yhuai @marmbrus

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rxin/spark explain

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/1123.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1123
    
----
commit a9d3ba877ce8920f0c4a348c6b32b1f4f7f39427
Author: Reynold Xin <rx...@apache.org>
Date:   2014-06-19T01:19:27Z

    [SPARK-2187] Explain should not run the optimizer twice.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by rxin <gi...@git.apache.org>.
Github user rxin commented on a diff in the pull request:

    https://github.com/apache/spark/pull/1123#discussion_r13949881
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/commands.scala ---
    @@ -71,16 +72,24 @@ case class SetCommand(
     }
     
     /**
    + * An explain command for users to see how a command will be executed.
    + *
    + * Note that this command takes in a logical plan, runs the optimizer on the logical plan
    + * (but do NOT actually execute it).
    + *
      * :: DeveloperApi ::
      */
     @DeveloperApi
     case class ExplainCommand(
    -    child: SparkPlan, output: Seq[Attribute])(
    +    logicalPlan: LogicalPlan, output: Seq[Attribute])(
         @transient context: SQLContext)
    -  extends UnaryNode with Command {
    +  extends LeafNode with Command {
     
    -  // Actually "EXPLAIN" command doesn't cause any side effect.
    -  override protected[sql] lazy val sideEffectResult: Seq[String] = this.toString.split("\n")
    +  // Run through the optimizer to generate the physical plan.
    +  // This is really side effect free but we follow the infrastructure anyway...
    --- End diff --
    
    I hope so ..... That was an old comment I just rewrote anyway ...


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/1123#issuecomment-46514306
  
    Merged build started. 


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by rxin <gi...@git.apache.org>.
Github user rxin commented on the pull request:

    https://github.com/apache/spark/pull/1123#issuecomment-46525610
  
    Ok I am merging this in master & branch-1.0.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/1123#issuecomment-46517788
  
    Merged build finished. 


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/1123#issuecomment-46514301
  
     Merged build triggered. 


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/1123#issuecomment-46525503
  
    All automated tests passed.
    Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15893/


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/1123#issuecomment-46522444
  
     Merged build triggered. 


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/spark/pull/1123


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/1123#issuecomment-46522447
  
    Merged build started. 


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/1123#issuecomment-46525501
  
    Merged build finished. All automated tests passed.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by marmbrus <gi...@git.apache.org>.
Github user marmbrus commented on a diff in the pull request:

    https://github.com/apache/spark/pull/1123#discussion_r13949859
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/commands.scala ---
    @@ -71,16 +72,24 @@ case class SetCommand(
     }
     
     /**
    + * An explain command for users to see how a command will be executed.
    + *
    + * Note that this command takes in a logical plan, runs the optimizer on the logical plan
    + * (but do NOT actually execute it).
    + *
      * :: DeveloperApi ::
      */
     @DeveloperApi
     case class ExplainCommand(
    -    child: SparkPlan, output: Seq[Attribute])(
    +    logicalPlan: LogicalPlan, output: Seq[Attribute])(
         @transient context: SQLContext)
    -  extends UnaryNode with Command {
    +  extends LeafNode with Command {
     
    -  // Actually "EXPLAIN" command doesn't cause any side effect.
    -  override protected[sql] lazy val sideEffectResult: Seq[String] = this.toString.split("\n")
    +  // Run through the optimizer to generate the physical plan.
    +  // This is really side effect free but we follow the infrastructure anyway...
    --- End diff --
    
    Is it?  Have we fixed all the bugs where generating a plan actually fires off Spark jobs?  :P


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by marmbrus <gi...@git.apache.org>.
Github user marmbrus commented on the pull request:

    https://github.com/apache/spark/pull/1123#issuecomment-46514203
  
    Nice, this LGTM.  This will also make it easy to possibly add the option to view the optimized logical plan though explain at some point as well.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] spark pull request: [SPARK-2187] Explain should not run the optimi...

Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:

    https://github.com/apache/spark/pull/1123#issuecomment-46517789
  
    
    Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15886/


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---