alamb opened a new pull request #8085: URL: https://github.com/apache/arrow/pull/8085
This is a proposal PR that I thought would be easier to do via PR rather than email. FYI @jorgecarleitao and @andygrove The context is that I plan to make `LogicalPlan` based on traits to allow extensibility, rather than a hard coded enum, to mirror how `ExecutionPlans` work. As an initial smalls step towards this goal, I propose consistent module naming for logical and physical plans So after this PR we have the top level modules: * logical_plan * physical_plan * optimizer (currently depends on both logical_plan and physical_plan) * execution (has context, and df) The logical change here is quite small: Commit 1 has the result of running these commands: ``` mkdir logical_plan git mv logicalplan.rs logical_plan/mod.rs git mv execution/physical_plan . ``` And the next two commits simply update all references to the new module locations, and the last formats the code for good measure As follow on PRs (as I define the LogicalPlanNode trait) I would likely propose splitting the logical_plan/mod.rs into other smaller modules. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
