gaojun2048 opened a new issue #1439:
URL: https://github.com/apache/arrow-datafusion/issues/1439


   **Is your feature request related to a problem or challenge? Please describe 
what you are trying to do.**
   Now, we can only create a datafusion execution context with default table 
information in ballista, we can't just create a new context because we need a 
context that has tables registered from previous SQL statements that have been 
executed.
   
![image](https://user-images.githubusercontent.com/32193458/145745802-45304fa6-c6ab-4f78-b167-e73476373343.png)
   
   
   **Describe the solution you'd like**
   If ExecutionContext support init ExecutionContextState with `new(state: 
Arc<Mutex<ExecutionContextState>>)` method, then we can manage this information 
in the ballista scheduler, and send this information to the ballista executor, 
where every datafusion ExecutionContext created in the ballista executor can be 
Have the same ExecutionContextState content.
   
   


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