Publically re-export rand
with test_utils
#7128
Open
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?
55.0.0
(Apr 2025) #7084Rationale for this change
As we found out here
rand
appears in some public APIs and thus it should be available to use with just arrowFor example, in DataFusion we have
https://github.com/apache/datafusion/blob/dfc4ba31ed26fbc84eebb0c39b96ebd8f2c11267/datafusion/functions-aggregate/benches/array_agg.rs#L51-L58
(namely randomly generating a LIstArray using the
create_primitive_array
function from bench_utils)Being able to have datafusion's benchmark use the same rand / distribution would let us use both versions
It may just be better to avoid using the arrow bench_utils at all.
What changes are included in this PR?
Propose publically re-exporting
rand
and using that re-export in the public APIsAre there any user-facing changes?
New public export when
test_utils
feature is enabled