maropu opened a new pull request #27229: [SPARK-29708][SQL][BRANCH-2.4] Correct 
aggregated values when grouping sets are duplicated
URL: https://github.com/apache/spark/pull/27229
 
 
   <!--
   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.
   -->
   
   ### 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 pr intends to fix wrong aggregated values in `GROUPING SETS` when there 
are duplicated grouping sets in a query (e.g., `GROUPING SETS ((k1),(k1))`).
   
   For example;
   ```
   scala> spark.table("t").show()
   +---+---+---+
   | k1| k2|  v|
   +---+---+---+
   |  0|  0|  3|
   +---+---+---+
   
   scala> sql("""select grouping_id(), k1, k2, sum(v) from t group by grouping 
sets ((k1),(k1,k2),(k2,k1),(k1,k2))""").show()
   +-------------+---+----+------+                                              
   
   |grouping_id()| k1|  k2|sum(v)|
   +-------------+---+----+------+
   |            0|  0|   0|     9| <---- wrong aggregate value and the correct 
answer is `3`
   |            1|  0|null|     3|
   +-------------+---+----+------+
   
   // PostgreSQL case
   postgres=#  select k1, k2, sum(v) from t group by grouping sets 
((k1),(k1,k2),(k2,k1),(k1,k2));
    k1 |  k2  | sum 
   ----+------+-----
     0 |    0 |   3
     0 |    0 |   3
     0 |    0 |   3
     0 | NULL |   3
   (4 rows)
   
   // Hive case
   hive> select GROUPING__ID, k1, k2, sum(v) from t group by k1, k2 grouping 
sets ((k1),(k1,k2),(k2,k1),(k1,k2));
   1    0       NULL    3
   0    0       0       3
   ```
   [MS SQL Server has the same behaviour with 
PostgreSQL](https://github.com/apache/spark/pull/26961#issuecomment-573638442). 
This pr follows the behaviour of PostgreSQL/SQL server; it adds one more 
virtual attribute in `Expand` for avoiding wrongly grouping rows with the same 
grouping ID.
   
   This is the #26961 backport  for `branch-2.4`
   
   ### 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 fix bugs.
   
   ### Does this PR introduce any user-facing change?
   <!--
   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 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.
   -->
   The existing 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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

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

Reply via email to