abnobdoss commented on PR #3387:
URL: https://github.com/apache/iceberg-python/pull/3387#issuecomment-4539397818

   Hey @paultmathew, thanks for the clarification. I’m curious whether your use 
case still has performance problems when the partition source column is 
included in `join_cols`, as I think you’re proposing here.
   
   My assumption is that in that case `create_match_filter` already includes 
exact predicates on the partition source column, so partition pruning should 
have enough information to fire. If it still doesn’t, is the issue that the 
exact `Or(And(EqualTo, ...), ...)` predicate is too expensive/large for 
planning rather than that the partition signal is missing?


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