alamb opened a new pull request, #6570:
URL: https://github.com/apache/arrow-datafusion/pull/6570

   # Which issue does this PR close?
   
   Part of https://github.com/apache/arrow-datafusion/issues/1754 (see 
https://github.com/apache/arrow-datafusion/issues/1754#issuecomment-1579410979)
   
   # Rationale for this change
   
   I am trying to extract `physical_plan` into its own crate to improve 
modularity and compile times
   
   I am also trying to make sure the organization of the DataFusion crate is 
easier to understand for beginners. 
   
   # What changes are included in this PR?
   Move `PhysicalPlanner` and related structures to `physical_planner` crate
   
   # Are these changes tested?
   
   Existing tests
   
   # Are there any user-facing changes?
   Yes, documentation is improved (the planner is no longer buried in a sub 
module). Also, if users used the PhysicalPlanner directly they will need to 
update their `use` path
   
   <!--
   If there are any breaking changes to public APIs, please add the `api 
change` label.
   -->


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

Reply via email to