Combine the optimization rules decorrelate, decorrelate_lateral_join, and decorrelate_predicate_subquery into one. #16073

Activity

1. irenjj

   added

   enhancementNew feature or requestNew feature or request

   on May 17, 2025
2. duongcongtoai commented on May 17, 2025

   

   duongcongtoai

   on May 17, 2025

   Contributor

   More actions

   Do you think this draft PR can combine all the rules?
   lateral join is not mentioned yet, but i think we can use the same data structure to reason the dependencies between the operator

   pub struct DependentJoinTracker {
       root: Option<usize>,
       // each logical plan traversal will assign it a integer id
       current_id: usize,
       // each newly visted operator is inserted inside this map for tracking
       nodes: IndexMap<usize, Operator>,
       // all the node ids from root to the current node
       // this is used during traversal only
       stack: Vec<usize>,
       // track for each column, the nodes/logical plan that reference to its within the tree
       accessed_columns: IndexMap<Column, Vec<ColumnAccess>>,
       alias_generator: Arc<AliasGenerator>,
   }
   

   👍React with 👍2Reacted by irenjj and Andrew Lamb
3. irenjj commented on May 18, 2025

   

   irenjj

   on May 18, 2025

   ContributorAuthor

   More actions

   Cool! Thanks @duongcongtoai, maybe we can support lateral join after #16016 merged.

   ❤️React with ❤️1Reacted by Duong Cong Toai
4. alamb commented on May 18, 2025

   

   alamb

   on May 18, 2025

   Contributor

   More actions

   I really like the idea of using #16016 / #5492 to satisfy this goal