gene-bordegaray commented on code in PR #20331:
URL: https://github.com/apache/datafusion/pull/20331#discussion_r2852487046


##########
datafusion/physical-expr/src/expressions/dynamic_filters.rs:
##########
@@ -86,6 +108,11 @@ struct Inner {
     /// This is redundant with the watch channel state, but allows us to 
return immediately
     /// from `wait_complete()` without subscribing if already complete.
     is_complete: bool,
+    /// Per-partition filter expressions for partition-index routing.
+    /// When both sides of a hash join preserve their file partitioning (no 
RepartitionExec(Hash)),
+    /// build-partition i corresponds to probe-partition i. This allows 
storing per-partition
+    /// filters so that each partition only sees its own bounds, giving 
tighter filtering.
+    partitioned_exprs: PartitionedFilters,
 }

Review Comment:
   Is the generic runtime binding for Physical Expressions not a good path 
forward? I have changed this some @adriangb  last review and think it will 
provide a clean API once the follow up work is done.
   
   It will eliminate the wrapper and create an API over any physical expression 
to have runtime properties. This feels like a good approach since it's easy to 
comprehend, no changes to the schema or injecting columns, and introduced what 
I think will be a useful property to physical expressions as cost based and 
adaptive query execution is adopted.
   
   Cc: @gabotechs 



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