alamb opened a new pull request, #23308:
URL: https://github.com/apache/datafusion/pull/23308

   ## Which issue does this PR close?
   - Part of https://github.com/apache/datafusion/issues/19241
   - part of https://github.com/apache/datafusion/issues/23307
   - Follow on to https://github.com/apache/datafusion/pull/23305
   
   ## Rationale for this change
   
   We are adding SQL-level coverage for the integer IN list specialization 
paths. https://github.com/apache/datafusion/pull/23305 adds the initial integer 
`IN` coverage.
   
   This PR adds paired `NOT IN` coverage so the SLT file also exercises the 
negated IN list implementation paths while keeping the expected results easy to 
audit.
   
   ## What changes are included in this PR?
   1. Add paired `NOT IN` checks for the existing integer IN list queries
   2. Compare `IN` and `NOT IN` with `<>` so non-null inverse results are 
expected to be `true`
   3. Cover the existing min, max, no-match, nullable-input, and null-in-list 
integer cases
   
   ## Are these changes tested?
   
   Only tests
   
   ## Are there any user-facing changes?
   
   No
   


-- 
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: [email protected]

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