tustvold opened a new pull request, #6169:
URL: https://github.com/apache/arrow-datafusion/pull/6169
# 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 #2504
# 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.
-->
Partly inspired by #6164, but the rayon-based scheduler in its current
incomplete incarnation provides minimal benefits over the current tokio-based
approach, and is a non-trivial amount of fairly complex code. Given this and
the fact I am unlikely to be able to find time to work on it in the next few
months, I think we should just remove it. We can always bring it or something
based on it back in the future should we wish to.
Whilst I still think the long-term vision of the scheduler of moving to a
push-based execution model would have been pretty compelling, at this stage it
is probably too difficult and intrusive to make such a change. Additionally,
whilst perhaps less architecturally elegant, we can likely get many of the
advantages by introducing interior parallelism to the existing operators (e.g.
#6162).
# 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.
-->
# Are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are
they covered by existing tests)?
-->
# 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]
