adriangb commented on PR #13795: URL: https://github.com/apache/datafusion/pull/13795#issuecomment-2552970356
> If we go one small step further and add `and col_a_min is not null and col_b_min is not null` then we actually ensure that the predicates always return `true` or `false` and never `null` which IMO would be helpful just to minimize confusion especially since the interpretation of `null` here is so confusing and opposes the interpretation of `null` in a `where` clause. Turns out not that small of a step: there's cases that previously pruned the row that no longer would, in particular when one statistic (`min` _or_ `max`) is missing but the other one isn't and we only use the non-missing statistic. -- 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: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
