yjshen opened a new issue #824: URL: https://github.com/apache/arrow-datafusion/issues/824
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** I'd like to propose making an `ExecutionContext` static and publicly accessible. Several cases would benefit from a global context: 1. We could have a protocol handler registry that users could plug in third-party protocol handlers at runtime, and get the physical operator execution logic to use the newly registered handler reading files in different remote stores, S3, HDFS for example. 2. When we consider controlling the total amount of memory Datafusion could use. All physical operators should register their memory usage with a global context, and try to allocate more memory or spill itself if used up all allowed memory. **Describe the solution you'd like** A single, global `ExecutionContext` that is inited on its first use and a getter to always returning the same instance. **Describe alternatives you've considered** Passing around a shared state/context to each operator needs it. For example, table scan, join, hash agg, and sort. **Additional context** Similar to the shared `SparkEnv` in each process (driver/executor) of Spark. -- 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]
