GitHub user kevinyu98 opened a pull request:

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

    [SPARK-18871][SQL][TESTS] New test cases for IN/NOT IN subquery 2nd batch

    ## What changes were proposed in this pull request?
    
    This is 2nd batch of test case for IN/NOT IN subquery.  In this PR, it has 
these test cases:
    `in-limit.sql`
    `in-order-by.sql`
    `not-in-group-by.sql`
    
    These are the queries and results from running on DB2.
    [in-limit DB2 
version](https://github.com/apache/spark/files/743267/in-limit.sql.db2.out.txt)
    [in-order-by DB2 
version](https://github.com/apache/spark/files/743269/in-order-by.sql.db2.txt)
    [not-in-group-by DB2 
version](https://github.com/apache/spark/files/743271/not-in-group-by.sql.db2.txt)
    [output of in-limit.sql 
DB2](https://github.com/apache/spark/files/743276/in-limit.sql.db2.out.txt)
    [output of in-order-by.sql 
DB2](https://github.com/apache/spark/files/743278/in-order-by.sql.db2.out.txt)
    [output of not-in-group-by.sql 
DB2](https://github.com/apache/spark/files/743279/not-in-group-by.sql.db2.out.txt)
    
    ## How was this patch tested?
    
    This pr is adding new test cases.

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

    $ git pull https://github.com/kevinyu98/spark spark-18871-2

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

    https://github.com/apache/spark/pull/16759.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 #16759
    
----

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to