Repository navigation
feat: impl Any for MemoryPool - #21803
Merged
Merged
Conversation
nathanb9
reviewed
Apr 23, 2026
| /// * [`TrackConsumersPool`]: Wraps another [`MemoryPool`] and tracks consumers, | ||
| /// providing better error messages on the largest memory users. | ||
| pub trait MemoryPool: Send + Sync + std::fmt::Debug + Display { | ||
| pub trait MemoryPool: Any + Send + Sync + std::fmt::Debug + Display { |
Contributor
There was a problem hiding this comment.
Adding Any as a supertrait adds a 'static requirement to every MemoryPool implementor. This might break downstream if they have implemented custom pools which borrowed state or lifetime parameters
Contributor
Author
There was a problem hiding this comment.
thank you for mention this, i add upgrade guide in 344b52f
nathanb9
approved these changes
Apr 23, 2026
|
Thank you for opening this pull request! Reviewer note: cargo-semver-checks reported the current version number is not SemVer-compatible with the changes in this pull request (compared against the base branch). Details |
xudong963
approved these changes
May 11, 2026
Contributor
Author
|
thanks for your reviews @xudong963 |
gstvg
pushed a commit
to gstvg/arrow-datafusion
that referenced
this pull request
May 14, 2026
## Which issue does this PR close? - Closes apache#21802 ## Rationale for this change - see apache#21802 ## What changes are included in this PR? implment Any for MemoryPool ## Are these changes tested? yes, add one test case ## Are there any user-facing changes? --------- Co-authored-by: Dmitrii Blaginin <[email protected]>
tsenart
pushed a commit
to perfloop-oss/datafusion
that referenced
this pull request
Nov 13, 2026
## Which issue does this PR close? - Closes apache#26633. ## Rationale for this change There is no way to tell which reader factory a `ParquetSource` uses. `parquet_file_reader_factory()` returns `&Arc<dyn ParquetFileReaderFactory>`, and the trait has no downcast path. ## What changes are included in this PR? `ParquetFileReaderFactory` gets `Any` as a supertrait, and `dyn ParquetFileReaderFactory` gets `is` and `downcast_ref`, like `dyn FileSource` in apache#21576. I also added a 57.0.0 upgrade guide entry, like the ones for `MemoryPool` (apache#21803) and `QueryPlanner` (apache#22241). ## What is the testing strategy for this PR? A unit test in `source.rs` sets each built-in factory on a `ParquetSource` and checks that `parquet_file_reader_factory()` downcasts to it. ## Are there any user-facing changes? Two new methods on `dyn ParquetFileReaderFactory`. The semver check will flag the new supertrait, but the trait already required `'static`, so existing implementations compile unchanged. Drafted with Claude. I reviewed the change and this text. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rationale for this change
What changes are included in this PR?
implment Any for MemoryPool
Are these changes tested?
yes, add one test case
Are there any user-facing changes?