westonpace opened a new issue, #34887:
URL: https://github.com/apache/arrow/issues/34887

   ### Describe the enhancement requested
   
   It is now possible to build Arrow without Acero.  An R minimal build will 
(once #34844 merges, assuming no changes) disable Acero.  This means that a lot 
of the functionality & tests will no longer work.
   
   Should we keep Acero out of the minimal build?  It's not super large 
(libarrow_acero is ~10% of the size of libarrow if ARROW_COMPUTE=ON)
   
   Currently, in the PR, I am skipping all dplyr tests.  This is mainly for 
simplicity so I can get the build working.  Some dplyr tests can still pass 
(even without Acero, compute functions still work).
   
   Do we want to try to more narrowly skip dplyr tests?  Do we want to say "if 
acero is disabled then don't try to do compute" or do we want to try and 
explain some nuance of "you can do these compute tasks without acero but these 
other compute tasks require acero"? 
   
   On the other hand, it is now possible to turn `ARROW_COMPUTE=OFF` and 
actually see some meaningful difference (all non-essential kernels are removed, 
cuts the size of the arrow binary almost in half).  Should we disable compute 
entirely in an R minimal build?
   
   ### Component(s)
   
   R


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