You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by dilipbiswal <gi...@git.apache.org> on 2017/03/08 19:12:18 UTC

[GitHub] spark pull request #17214: [SQL][MINOR] The analyzer rules are fired twice f...

GitHub user dilipbiswal opened a pull request:

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

    [SQL][MINOR] The analyzer rules are fired twice for cases when AnalysisException is raised from analyzer.

    ## What changes were proposed in this pull request?
    In general we have a checkAnalysis phase which validates the logical plan and throw AnalysisException on semantic errors. However we also can throw AnalysisException from a few analyzer rules like ResolveSubquery.
    
    I found that we fire up the analyzer rule twice for the queries that throw AnalysisException from one of the analyzer rules. This is a very minor fix. We don't have to strictly fix it. I just got confused seeing the rule getting fired two times when i was not expecting it. 
    
    ## How was this patch tested?
    
    Tested manually.

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

    $ git pull https://github.com/dilipbiswal/spark analyis_twice

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

    https://github.com/apache/spark/pull/17214.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 #17214
    
----
commit 86582ef421818110a3c2f4705a9e461dd9a17ffe
Author: Dilip Biswal <db...@us.ibm.com>
Date:   2017-03-08T19:02:02Z

    [SQL][MINOR] The analyzer rules are fired twice for cases AnalysisException is raised from analyzer rules

----


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [MINOR][SQL] The analyzer rules are fired twice for case...

Posted by dilipbiswal <gi...@git.apache.org>.
Github user dilipbiswal commented on the issue:

    https://github.com/apache/spark/pull/17214
  
    Thank you @gatorsmile @cloud-fan @hvanhovell 


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r105027190
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    --- End diff --
    
    @cloud-fan Actually thats what i also thought Wenchen. But it seems like if an exception occurred before the assignment to lazy val happens , then it treats it like the first evaluation never happened ?


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [MINOR][SQL] The analyzer rules are fired twice for case...

Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the issue:

    https://github.com/apache/spark/pull/17214
  
    **[Test build #74228 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74228/testReport)** for PR 17214 at commit [`0dee6dd`](https://github.com/apache/spark/commit/0dee6dd3a81acab8524eb811522b5c9dacc3cee5).
     * This patch passes all tests.
     * This patch merges cleanly.
     * This patch adds no public classes.


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r105000659
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    --- End diff --
    
    @cloud-fan Yeah wenchen. so first time we invoke analyzer is on this line. And upon exception we go to catch block -
    ```
         case e: AnalysisException =>
           val ae = new AnalysisException(e.message, e.line, e.startPosition, Some(analyzed))
    ```
    and call analyzer the second time while trying to evaluate the last parameter - Some(analyzed) ?


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [MINOR][SQL] The analyzer rules are fired twice for case...

Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the issue:

    https://github.com/apache/spark/pull/17214
  
    **[Test build #74219 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74219/testReport)** for PR 17214 at commit [`86582ef`](https://github.com/apache/spark/commit/86582ef421818110a3c2f4705a9e461dd9a17ffe).
     * This patch passes all tests.
     * This patch merges cleanly.
     * This patch adds no public classes.


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r104999542
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    --- End diff --
    
    isn't analyzed a lazy val?


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r105030136
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    --- End diff --
    
    so we just need a line before this line, to materialize `analyzed`.


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [MINOR][SQL] The analyzer rules are fired twice for case...

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

    https://github.com/apache/spark/pull/17214
  
    Merged build finished. Test 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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r105047064
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    +    var analyzedPlan: Option[LogicalPlan] = None
    --- End diff --
    
    Ahh, we want it materialized outside the block. Yeah, in that case wenchen's suggestion is the way to go



---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [MINOR][SQL] The analyzer rules are fired twice for case...

Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the issue:

    https://github.com/apache/spark/pull/17214
  
    **[Test build #74219 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74219/testReport)** for PR 17214 at commit [`86582ef`](https://github.com/apache/spark/commit/86582ef421818110a3c2f4705a9e461dd9a17ffe).


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [MINOR][SQL] The analyzer rules are fired twice for case...

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

    https://github.com/apache/spark/pull/17214
  
    Merged build finished. Test 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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r105046388
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    +    var analyzedPlan: Option[LogicalPlan] = None
    --- End diff --
    
    @hvanhovell I tried the suggested code snippet. Actually since AnalyzedPlan is declared lazy the evaluation happens inside the try block and hence it has the same problem. So lets just move analyzed outside the try block as wenchen suggests ?
    
    ```scala
    def assertAnalyzed(): Unit = {
        analyzed
        try {
          sparkSession.sessionState.analyzer.checkAnalysis(analyzed)
        } catch {
          case e: AnalysisException =>
            val ae = new AnalysisException(e.message, e.line, e.startPosition, Option(analyzed))
            ae.setStackTrace(e.getStackTrace)
            throw ae
        }
      }
    ```


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [MINOR][SQL] The analyzer rules are fired twice for case...

Posted by gatorsmile <gi...@git.apache.org>.
Github user gatorsmile commented on the issue:

    https://github.com/apache/spark/pull/17214
  
    Thanks! Merging to master/2.1


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r105037075
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    +    var analyzedPlan: Option[LogicalPlan] = None
    --- End diff --
    
    You could make this a local lazy val. That should be a bit more concise. For example:
    ```scala
    def assertAnalyzed(): Unit = {
      lazy val analyzedPlan = analyzed
      try {
        sparkSession.sessionState.analyzer.checkAnalysis(analyzedPlan.get)
      } catch {
        case e: AnalysisException =>
          val ae = new AnalysisException(e.message, e.line, e.startPosition, Option(analyzedPlan))
          ae.setStackTrace(e.getStackTrace)
          throw ae
      }
    }
    ```


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [MINOR][SQL] The analyzer rules are fired twice for case...

Posted by gatorsmile <gi...@git.apache.org>.
Github user gatorsmile commented on the issue:

    https://github.com/apache/spark/pull/17214
  
    LGTM


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r105037287
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    --- End diff --
    
    put `analyzed` out of the try catch


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r105025960
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    --- End diff --
    
    isn't `lazy val` will only be evaluated 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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r105033548
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    --- End diff --
    
    @cloud-fan did you mean like this ?
    ```scala
    def assertAnalyzed(): Unit = {
        try {
          analyzed
          sparkSession.sessionState.analyzer.checkAnalysis(analyzed)
        } catch {
          case e: AnalysisException =>
            val ae = new AnalysisException(e.message, e.line, e.startPosition, Some(analyzed))
            ae.setStackTrace(e.getStackTrace)
            throw ae
        }
      }
    ```
    If so, it also causes two invocation like before. 


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

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


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [SQL][MINOR] The analyzer rules are fired twice for case...

Posted by dilipbiswal <gi...@git.apache.org>.
Github user dilipbiswal commented on the issue:

    https://github.com/apache/spark/pull/17214
  
    cc @gatorsmile @cloud-fan Please let me know your thoughts.


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [MINOR][SQL] The analyzer rules are fired twice for case...

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

    https://github.com/apache/spark/pull/17214
  
    Test PASSed.
    Refer to this link for build results (access rights to CI server needed): 
    https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74219/
    Test 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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r105047697
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    +    var analyzedPlan: Option[LogicalPlan] = None
    --- End diff --
    
    @hvanhovell Thank you.


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark pull request #17214: [MINOR][SQL] The analyzer rules are fired twice f...

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

    https://github.com/apache/spark/pull/17214#discussion_r105044269
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
    @@ -46,9 +46,13 @@ class QueryExecution(val sparkSession: SparkSession, val logical: LogicalPlan) {
       protected def planner = sparkSession.sessionState.planner
     
       def assertAnalyzed(): Unit = {
    -    try sparkSession.sessionState.analyzer.checkAnalysis(analyzed) catch {
    +    var analyzedPlan: Option[LogicalPlan] = None
    --- End diff --
    
    Thanks you @cloud-fan @hvanhovell. I will make the change.


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [MINOR][SQL] The analyzer rules are fired twice for case...

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

    https://github.com/apache/spark/pull/17214
  
    Test PASSed.
    Refer to this link for build results (access rights to CI server needed): 
    https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74228/
    Test 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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org


[GitHub] spark issue #17214: [MINOR][SQL] The analyzer rules are fired twice for case...

Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the issue:

    https://github.com/apache/spark/pull/17214
  
    **[Test build #74228 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74228/testReport)** for PR 17214 at commit [`0dee6dd`](https://github.com/apache/spark/commit/0dee6dd3a81acab8524eb811522b5c9dacc3cee5).


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org