mingmwang opened a new pull request #2091:
URL: https://github.com/apache/arrow-datafusion/pull/2091
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #1862.
# Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
# What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
This is the part3 of the PR. It covers the below parts:
1. Avoid using ``` &mut` self ``` in SessionContext methods, trivial UT
fixes
2. Remove the global SessionContext from Ballista SchedulerServer, add
SessionContextRegistry to Scheduler to manage multiple running sessions.
3. Remove the global SessionContext from Ballista Executor, implement
FunctionRegistry for TaskContext.
4. Ballista proto grpc API changes, add ```optional_session_id``` to
```ExecuteQueryParams```, add session_id and props to ```TaskDefinition```.
Create new SessionContext for the first time of the query and reuse the
existing SessionContext for ongoing queries for a users.
5. Propagate the session configurations from Ballista Client to Ballista
Scheduler and to Executors.
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
--
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]
