Fix test feature selection so all feature combinations work as expected #6626
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?
Some combinations of features cause compilation failures or test failures where not necessary. For example, in the
parquet/src/file/metadata/reader.rs
file, theMetadataFetch
trait is only imported whenfeature = "async"
, but that trait exists under a module that's markedfeature = "arrow"
, so we need to enable both those features to get it to work.Rationale for this change
There's nothing stopping people from using any combination of features from this crate, so we should make sure they're all supported
What changes are included in this PR?
This just adds extra
#[cfg()]
attributes where necessary to fix compilation and test failures.Are there any user-facing changes?
No. It looks, on the surface, like we could be breaking the parquet crate for people who have the
async
flag enabled with thearrow
flag disabled, but this crate doesn't compile in its current form for that combination, so this won't actually adversely affect anyone.