We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RepartitionExec
Describe the bug See https://github.com/apache/arrow-datafusion/blob/5b70e3543f5c10832e43ed25e7d4166cf0c1df78/datafusion/core/src/physical_plan/repartition.rs#L333-L340
To Reproduce -
Expected behavior The data kept in these channels should be registered with the MemoryManager.
MemoryManager
Additional context -
The text was updated successfully, but these errors were encountered:
I'm working on this.
Sorry, something went wrong.
fix: account for memory in RepartitionExec
3ee4902
Fixes apache#4816.
fix: account for memory in RepartitionExec (#4820)
83c1026
* refactor: explicit loop instead of (tail) recursion * test: simplify * fix: account for memory in `RepartitionExec` Fixes #4816. * fix: sorting memory limit test
Successfully merging a pull request may close this issue.
Describe the bug
See https://github.com/apache/arrow-datafusion/blob/5b70e3543f5c10832e43ed25e7d4166cf0c1df78/datafusion/core/src/physical_plan/repartition.rs#L333-L340
To Reproduce
-
Expected behavior
The data kept in these channels should be registered with the
MemoryManager
.Additional context
-
The text was updated successfully, but these errors were encountered: