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 2022/03/07 21:08:32 UTC

[GitHub] [arrow-datafusion] alamb commented on pull request #1924: Refactor ExecutionContext and related conf to support multi-tenancy configurations

alamb commented on pull request #1924:
URL: https://github.com/apache/arrow-datafusion/pull/1924#issuecomment-1061137810


   I think another consideration is 
   
   I agree with @yjshen (and I think @thinkharderdev ) that for the datafusion (use as a library) feature, a single static `RuntimeEnv` is a challenge because of how many different ways it may be deployed / embedded.  I can imagine people using DataFusion to build systems that attempt to build in isolation (by using separate `RuntimeEnv` for different subsets of users / queries) as well as systems that use other technologies (e.g. kubernetes) to implement isolation
   
   I think passing around the `RuntimeEnv` is the most flexible, if annoying, approach.
   
   I also wanted to reiterate that I liked pretty much all of the rest of this PR (like adding TaskContext, SessionContext, cleanups, etc) so perhaps we can proceed with adding in those pieces incrementall while we work out the "global" vs "non global" context thing


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