feat(memory-tracking): expose API to NullBuffer, ArrayData, and Array #8918
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?
Part of #8137. Follow up of #7303. Replaces #8040.
Rationale for this change
#7303 implements the fundamental symbols for tracking memory. This patch exposes those APIs to a higher level Array and ArrayData.
What changes are included in this PR?
New
claimAPI for NullBuffer, ArrayData, and Array. Newpoolfeature-flag to arrow, arrow-array, and arrow-data.Are these changes tested?
Added a doctest on the
Array::claimmethod.Are there any user-facing changes?
Added API and a new feature-flag for arrow, arrow-array, and arrow-data.