mingmwang opened a new issue #1848: URL: https://github.com/apache/arrow-datafusion/issues/1848
**Describe the bug** The issue is caused by the changes [1677](https://github.com/apache/arrow-datafusion/pull/1677) which always use the ExecutionContext from the SchedulerServer. Before the change, run TPCH benchmark Q1 on Ballista: [2022-02-16T08:47:59Z INFO ballista_scheduler] Adding stage 1 with 1 pending tasks [2022-02-16T08:47:59Z INFO ballista_scheduler] Adding stage 2 with 2 pending tasks [2022-02-16T08:47:59Z INFO ballista_scheduler] Adding stage 3 with 1 pending tasks After the change: [2022-02-16T08:44:57Z INFO ballista_scheduler] Adding stage 1 with 1 pending tasks [2022-02-16T08:44:57Z INFO ballista_scheduler] Adding stage 2 with 8 pending tasks [2022-02-16T08:44:57Z INFO ballista_scheduler] Adding stage 3 with 1 pending tasks. A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: **Expected behavior** SchedulerServer should honor the configuration settings from the ExecuteQueryParams. **Additional context** Add any other context about the problem 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
