You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2021/08/08 05:30:21 UTC

[GitHub] [arrow-datafusion] houqp edited a comment on issue #824: A global, shared `ExecutionContext`

houqp edited a comment on issue #824:
URL: https://github.com/apache/arrow-datafusion/issues/824#issuecomment-894745875


   If it's for memory control, perhaps we could extend `ExecutionPlan`'s `execute` method to take an extra `ExecutionContext` as a second argument? Then within each physical operator's implementation, we can have the operator access the passed in context for memory control.
   
   @jorgecarleitao @andygrove @alamb @Dandandan for the context, @yjshen is working on a native spark executor using Datafusion: https://the-asf.slack.com/archives/C01QUFS30TD/p1621582734043500.
   
   Executor memory control would be very relevant to ballista as well, so I am curious if @andygrove has any opinion on what's the right abstraction here.
   
   


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