david-mollitor-db opened a new pull request, #58794: URL: https://github.com/apache/spark/pull/58794
### What changes were proposed in this pull request? Update the `spark.sql.parquet.pushdown.inFilterThreshold` config documentation to match the current implementation. The doc still states that, when an IN list exceeds the threshold, the Parquet filter is pushed down as a range (a value `>= min AND <= max`). That range was removed by SPARK-39312, which replaced it with a single native Parquet `in` predicate (`FilterApi.in`) over the set of values. This is a documentation-only change. ### Why are the changes needed? The doc is stale and misleading. `ParquetFilters` no longer pushes a `[min, max]` range for above-threshold IN lists -- it pushes `FilterApi.in(column, set)` (via `makeInPredicate`). The `.doc(...)` string predates SPARK-39312 and describes behavior that no longer exists, which misrepresents the pruning precision of large IN filters. ### Does this PR introduce _any_ user-facing change? No. Documentation-only update to a config description; no behavior change. ### How was this patch tested? No tests. Documentation-only change to a `.doc(...)` string; confirmed the current `ParquetFilters` uses `FilterApi.in` for above-threshold IN lists (introduced by SPARK-39312) rather than a min/max range. ### Was this patch authored or co-authored using generative AI tooling? This pull request and its description were written by Isaac. -- 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]
