You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by "cloud-fan (via GitHub)" <gi...@apache.org> on 2023/02/23 03:55:04 UTC

[GitHub] [spark] cloud-fan opened a new pull request, #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning

cloud-fan opened a new pull request, #40137:
URL: https://github.com/apache/spark/pull/40137

   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: https://spark.apache.org/contributing.html
     2. Ensure you have added or run the appropriate tests for your PR: https://spark.apache.org/developer-tools.html
     3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP][SPARK-XXXX] Your PR title ...'.
     4. Be sure to keep the PR description updated to reflect all changes.
     5. Please write your PR title to summarize what this PR proposes.
     6. If possible, provide a concise example to reproduce the issue for a faster review.
     7. If you want to add a new configuration, please read the guideline first for naming configurations in
        'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
     8. If you want to add or modify an error type or message, please read the guideline first in
        'core/src/main/resources/error/README.md'.
   -->
   
   ### What changes were proposed in this pull request?
   <!--
   Please clarify what changes you are proposing. The purpose of this section is to outline the changes and how this PR fixes the issue. 
   If possible, please consider writing useful notes for better and faster reviews in your PR. See the examples below.
     1. If you refactor some codes with changing classes, showing the class hierarchy will help reviewers.
     2. If you fix some SQL features, you can provide some references of other DBMSes.
     3. If there is design documentation, please add the link.
     4. If there is a discussion in the mailing list, please add the link.
   -->
   This is a follow-up of https://github.com/apache/spark/pull/37525 . When the project list as aliases, we go to the `projectExpression` branch which filters away invalid partitioning/ordering that reference non-existing attributes in the current plan node. However, this filtering is missing when the project list has no alias, where we directly return the child partitioning/ordering.
   
   This PR fixes it.
   
   ### Why are the changes needed?
   <!--
   Please clarify why the changes are needed. For instance,
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, you can clarify why it is a bug.
   -->
   to make sure we always return valid output partitioning/ordering.
   
   ### Does this PR introduce _any_ user-facing change?
   <!--
   Note that it means *any* user-facing change including all aspects such as the documentation fix.
   If yes, please clarify the previous behavior and the change this PR proposes - provide the console output, description and/or an example to show the behavior difference if possible.
   If possible, please also clarify if this is a user-facing change compared to the released Spark versions or within the unreleased branches such as master.
   If no, write 'No'.
   -->
   no
   
   ### How was this patch tested?
   <!--
   If tests were added, say they were added here. Please make sure to add some test cases that check the changes thoroughly including negative and positive cases if possible.
   If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future.
   If tests were not added, please describe why they were not added and/or why it was difficult to add.
   If benchmark tests were added, please run the benchmarks in GitHub Actions for the consistent environment, and the instructions could accord to: https://spark.apache.org/developer-tools.html#github-workflow-benchmarks.
   -->
   new tests


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

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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


[GitHub] [spark] dongjoon-hyun commented on pull request #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning

Posted by "dongjoon-hyun (via GitHub)" <gi...@apache.org>.
dongjoon-hyun commented on PR #40137:
URL: https://github.com/apache/spark/pull/40137#issuecomment-1442143437

   Oh is it still failing?


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

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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


[GitHub] [spark] viirya commented on pull request #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning

Posted by "viirya (via GitHub)" <gi...@apache.org>.
viirya commented on PR #40137:
URL: https://github.com/apache/spark/pull/40137#issuecomment-1442126791

   Hmm, the failed test seems a related one.


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

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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


[GitHub] [spark] cloud-fan commented on pull request #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning

Posted by "cloud-fan (via GitHub)" <gi...@apache.org>.
cloud-fan commented on PR #40137:
URL: https://github.com/apache/spark/pull/40137#issuecomment-1442699291

   The failed test checks invalid ordering and I've updated it.


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

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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


[GitHub] [spark] cloud-fan commented on pull request #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning

Posted by "cloud-fan (via GitHub)" <gi...@apache.org>.
cloud-fan commented on PR #40137:
URL: https://github.com/apache/spark/pull/40137#issuecomment-1441186992

   cc @peter-toth 


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

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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


[GitHub] [spark] cloud-fan commented on a diff in pull request #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning

Posted by "cloud-fan (via GitHub)" <gi...@apache.org>.
cloud-fan commented on code in PR #40137:
URL: https://github.com/apache/spark/pull/40137#discussion_r1115678677


##########
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/AliasAwareOutputExpression.scala:
##########
@@ -114,7 +114,11 @@ trait AliasAwareQueryOutputOrdering[T <: QueryPlan[T]]
         }
       }.takeWhile(_.isDefined).flatten.toSeq
     } else {
-      orderingExpressions
+      // Make sure the returned ordering are valid (only reference output attributes of the current

Review Comment:
   good point!



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

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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


[GitHub] [spark] viirya commented on pull request #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning

Posted by "viirya (via GitHub)" <gi...@apache.org>.
viirya commented on PR #40137:
URL: https://github.com/apache/spark/pull/40137#issuecomment-1442165227

   I think it was failing due to latest commit.


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

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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


[GitHub] [spark] dongjoon-hyun closed pull request #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning

Posted by "dongjoon-hyun (via GitHub)" <gi...@apache.org>.
dongjoon-hyun closed pull request #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning
URL: https://github.com/apache/spark/pull/40137


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

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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


[GitHub] [spark] peter-toth commented on a diff in pull request #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning

Posted by "peter-toth (via GitHub)" <gi...@apache.org>.
peter-toth commented on code in PR #40137:
URL: https://github.com/apache/spark/pull/40137#discussion_r1115359045


##########
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/AliasAwareOutputExpression.scala:
##########
@@ -114,7 +114,11 @@ trait AliasAwareQueryOutputOrdering[T <: QueryPlan[T]]
         }
       }.takeWhile(_.isDefined).flatten.toSeq
     } else {
-      orderingExpressions
+      // Make sure the returned ordering are valid (only reference output attributes of the current

Review Comment:
   Good catch! Thanks for this follow-up!
   
   But, I'm not sure this part is correct as `sortOrder.children` should be filtered with `_.references.subsetOf(outputSet)` separately.
   
   E.g. this test (is a bit artifical though) fails now:
   ```
     test("SPARK-42049: Improve AliasAwareOutputExpression - no alias but still prune expressions 2") {
       withSQLConf(SQLConf.OPTIMIZER_EXCLUDED_RULES.key ->
         Seq(CollapseProject.ruleName, ColumnPruning.ruleName).mkString(",")) {
         val df = spark.range(2).select($"id" as "a", $"id" as "b").select($"a")
         val outputOrdering = df.queryExecution.optimizedPlan.outputOrdering
   
         assert(outputOrdering.size == 1)
         assert(outputOrdering.head.child.asInstanceOf[Attribute].name == "a")
         assert(outputOrdering.head.sameOrderExpressions.size == 0)
       }
     }
   ```



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

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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


[GitHub] [spark] peter-toth commented on a diff in pull request #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning

Posted by "peter-toth (via GitHub)" <gi...@apache.org>.
peter-toth commented on code in PR #40137:
URL: https://github.com/apache/spark/pull/40137#discussion_r1115359045


##########
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/AliasAwareOutputExpression.scala:
##########
@@ -114,7 +114,11 @@ trait AliasAwareQueryOutputOrdering[T <: QueryPlan[T]]
         }
       }.takeWhile(_.isDefined).flatten.toSeq
     } else {
-      orderingExpressions
+      // Make sure the returned ordering are valid (only reference output attributes of the current

Review Comment:
   Good catch! Thanks for this follow-up!
   
   But, I'm not sure this part is correct as `sortOrder.children`s should be filtered with `_.references.subsetOf(outputSet)` separately.
   
   E.g. this test (is a bit artifical though) fails now:
   ```
     test("SPARK-42049: Improve AliasAwareOutputExpression - no alias but still prune expressions 2") {
       withSQLConf(SQLConf.OPTIMIZER_EXCLUDED_RULES.key ->
         Seq(CollapseProject.ruleName, ColumnPruning.ruleName).mkString(",")) {
         val df = spark.range(2).select($"id" as "a", $"id" as "b").select($"a")
         val outputOrdering = df.queryExecution.optimizedPlan.outputOrdering
   
         assert(outputOrdering.size == 1)
         assert(outputOrdering.head.child.asInstanceOf[Attribute].name == "a")
         assert(outputOrdering.head.sameOrderExpressions.size == 0)
       }
     }
   ```



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

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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


[GitHub] [spark] dongjoon-hyun commented on pull request #40137: [SPARK-42049][SQL][FOLLOWUP] Always filter away invalid ordering/partitioning

Posted by "dongjoon-hyun (via GitHub)" <gi...@apache.org>.
dongjoon-hyun commented on PR #40137:
URL: https://github.com/apache/spark/pull/40137#issuecomment-1442846535

   Merged to master/3.4.
   Thank you, @cloud-fan , @peter-toth , @viirya .


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

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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