alamb commented on issue #17719: URL: https://github.com/apache/datafusion/issues/17719#issuecomment-3377322069
> To be able to plug in custom implementations we somehow need an interface(trait) for that. I could think of the following ways to do this: Thanks @JanKaul and @LorrensP-2158466 > Additional JoinGraphPlanner trait I think this one makes sense as it is the most flexible. Making `JoinGraph` itself a trait seems like it might make it hard to reuse a common query representation Typically I have seen join order planning / enumeration implemented as a graph walk over the JoinGraph (e.g. a breadth first walk). To @LorrensP-2158466 's point, planning multi-way joins can be represented by finding a join with multiple input edges (predicates on multiple tables) and finding a covering set -- 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]
