2010YOUY01 commented on code in PR #19609: URL: https://github.com/apache/datafusion/pull/19609#discussion_r2681656047
########## datafusion/physical-expr-common/src/physical_expr/statistics_vectorized.rs: ########## @@ -0,0 +1,539 @@ +// Licensed to the Apache Software Foundation (ASF) under one +// or more contributor license agreements. See the NOTICE file +// distributed with this work for additional information +// regarding copyright ownership. The ASF licenses this file +// to you under the Apache License, Version 2.0 (the +// "License"); you may not use this file except in compliance +// with the License. You may obtain a copy of the License at +// +// http://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, +// software distributed under the License is distributed on an +// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +// KIND, either express or implied. See the License for the +// specific language governing permissions and limitations +// under the License. + +// Pruner Common Structs/Utilities + +//! This is the top-level comment for pruning via statistics propagation. +//! +//! TODO: This is a concise draft; it should be polished for readers with less +//! prior background. +//! +//! # Introduction +//! +//! This module helps skip scanning data micro-partitions by evaluating predicates +//! against container-level statistics. +//! +//! It supports pruning for complex and nested predicates through statistics +//! propagation. +//! +//! For examples of pruning nested predicates via statistics propagation, see: +//! <https://github.com/apache/datafusion/issues/19487> +//! +//! +//! +//! # Vectorized pruning intermediate representation +//! +//! Source statistics and intermediate pruning results are stored in Arrow arrays, +//! enabling vectorized evaluation across many containers. +//! +//! +//! +//! # Difference from [`super::PhysicalExpr::evaluate_bounds`] +//! +//! `evaluate_bounds()` derives per-column statistics for a single plan, aimed at +//! tasks like cardinality estimation and other planner fast paths. It reasons +//! about one container and may track richer distribution details. +//! Pruning must reason about *all* containers (potentially thousands) to decide +//! which to skip, so it favors a vectorized, array-backed representation with +//! lighter-weight stats. These are intentionally separate interfaces. +//! +//! +//! +//! # Core API/Data Structures +//! +//! The key structures involved in pruning are: Review Comment: Added a link in [6741a2a](https://github.com/apache/datafusion/pull/19609/commits/6741a2abd1466eaf25f9799d052345a6c6753976) -- 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]
