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

   ## Which issue does this PR close?
   
   - Part of #19241.
   - This PR was originally proposed as the first commit in the broader `IN 
LIST` optimization series in #19390.
   - This PR builds on the refactor extracted in #21649.
   
   ## Rationale for this change
   
   After #21649, non-primitive constant `IN LIST` evaluation still uses the 
extracted `ArrayStaticFilter` fallback path. That path relies on comparator 
checks for each input row. This PR replaces that fallback lookup with a 
precomputed hash table and shared result construction so generic constant-list 
evaluation is cheaper before the later specialized primitive and string 
optimizations from #19390.
   
   ## What changes are included in this PR?
   
   - Adds `expressions/in_list/result.rs` with shared `BooleanArray` 
construction for precomputed contains results.
   - Changes `ArrayStaticFilter` to build a `hashbrown::HashTable` over 
non-null constant-list entries and probe it per input value.
   - Keeps dictionary handling, null semantics, negation semantics, and 
primitive filter dispatch unchanged.
   - Wires the new result module into the existing `in_list` module tree.
   
   ## Are these changes tested?
   
   Yes. I validated this PR with:
   
   - `cargo fmt --all`
   - `cargo clippy -p datafusion-physical-expr --all-targets --all-features -- 
-D warnings`
   - `cargo test -p datafusion-physical-expr --all-features in_list`
   
   ## Are there any user-facing changes?
   
   No. This is an internal performance optimization only.


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