ExecutionContext.create_logical_plan currently returns an optimized plan.
There is already a separate method on ExecutionContext for creating an optimized plan and it would be better to have create_logical_plan return the unoptimized plan. This helps with testing and also helps for my use case where I want to pass the logical plan to another node before it gets optimized (it is not currently possible to optimize a plan twice, and this is causing me some issues)
Reporter: Andy Grove / @andygrove
Assignee: Andy Grove / @andygrove
Note: This issue was originally created as ARROW-5948. Please see the migration documentation for further details.