[GitHub] [arrow] westonpace commented on pull request #34575: GH-15280: [C++] Second block of refactoring to move acero out of libarrow

["westonpace (via GitHub)" <gi...@apache.org>]

westonpace commented on PR #34575:
URL: https://github.com/apache/arrow/pull/34575#issuecomment-1470920713

   > Got it - makes sense to me. @westonpace does that sound about right?
   
   Yes, `expression` is pretty stable.  So if the goal is a stable "compute" module then I think moving it inside `compute` should be safe.
   
   Thinking beyond just "stability" I think there is a pretty reasonable separation in Arrow between "compute functions" and "the execution engine" and I think it makes sense for `Expression` to live in the former.  There is also some desire for a Substrait API for expression evaluation.  In theory that could be done without "exec" but that would require splitting the substrait module into two pieces and I don't think that's worth our time (e.g. the expression evaluation API can just depend on "exec" even though it doesn't strictly need to)


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org