sarutak opened a new pull request #30755:
URL: https://github.com/apache/spark/pull/30755


   ### 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 reverts #30628 because AQE seems to sometimes generate wrong results.
   
   You can reproduce this issue with the following query ( this is taken from 
`scalar-subquery-select.sql`).
   ```
   create temporary view t3 as select * from values
     ('val3a', 6S, 12, 110L, float(15), 20D, 20E2, timestamp '2014-04-04 
01:02:00.000', date '2014-04-04'),
     ('val3a', 6S, 12, 10L, float(15), 20D, 20E2, timestamp '2014-05-04 
01:02:00.000', date '2014-05-04'),
     ('val1b', 10S, 12, 219L, float(17), 25D, 26E2, timestamp '2014-05-04 
01:02:00.000', date '2014-05-04'),
     ('val1b', 10S, 12, 19L, float(17), 25D, 26E2, timestamp '2014-05-04 
01:02:00.000', date '2014-05-04'),
     ('val1b', 8S, 16, 319L, float(17), 25D, 26E2, timestamp '2014-06-04 
01:02:00.000', date '2014-06-04'),
     ('val1b', 8S, 16, 19L, float(17), 25D, 26E2, timestamp '2014-07-04 
01:02:00.000', date '2014-07-04'),
     ('val3c', 17S, 16, 519L, float(17), 25D, 26E2, timestamp '2014-08-04 
01:02:00.000', date '2014-08-04'),
     ('val3c', 17S, 16, 19L, float(17), 25D, 26E2, timestamp '2014-09-04 
01:02:00.000', date '2014-09-05'),
     ('val1b', null, 16, 419L, float(17), 25D, 26E2, timestamp '2014-10-04 
01:02:00.000', null),
     ('val1b', null, 16, 19L, float(17), 25D, 26E2, timestamp '2014-11-04 
01:02:00.000', null),
     ('val3b', 8S, null, 719L, float(17), 25D, 26E2, timestamp '2014-05-04 
01:02:00.000', date '2014-05-04'),
     ('val3b', 8S, null, 19L, float(17), 25D, 26E2, timestamp '2015-05-04 
01:02:00.000', date '2015-05-04')
     as t3(t3a, t3b, t3c, t3d, t3e, t3f, t3g, t3h, t3i);
   
   SELECT (SELECT min(t3d) FROM t3);
   
   spark-sql> SELECT (SELECT min(t3d) FROM t3);
   10
   Time taken: 0.149 seconds, Fetched 1 row(s)
   spark-sql> SELECT (SELECT min(t3d) FROM t3);
   10
   Time taken: 0.116 seconds, Fetched 1 row(s)
   spark-sql> SELECT (SELECT min(t3d) FROM t3);
   10
   Time taken: 0.088 seconds, Fetched 1 row(s)
   spark-sql> SELECT (SELECT min(t3d) FROM t3);
   10
   Time taken: 0.109 seconds, Fetched 1 row(s)
   spark-sql> SELECT (SELECT min(t3d) FROM t3);
   0                                                                            
      <--------------- wrong result.
   Time taken: 0.103 seconds, Fetched 1 row(s)
   spark-sql> SELECT (SELECT min(t3d) FROM t3);
   10
   Time taken: 0.11 seconds, Fetched 1 row(s)
   ```
   
   ### 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.
   -->
   This is a serious bug.
   
   ### 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'.
   -->
   Yes.
   
   ### 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.
   -->
   I confirmed I never get the wrong result with 
`spark.sql.adaptive.enabled=false`.


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