GH-45034: [C++] Remove Parquet requirement from Arrow Acero and from Arrow Dataset when not necessary #45035
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.
Rationale for this change
Currently we are defining Parquet as a requirement for Acero and for Dataset on
ArrowAceroConfig.cmake.in
andArrowDatasetConfig.cmake.in
respectively.Parquet should never be necessary for Acero and could be necessary for Dataset only if it has been built with Parquet support.
What changes are included in this PR?
Remove Parquet from
ArrowAceroConfig.cmake.in
and add it as optional dependency forArrowDatasetConfig.cmake.in
Are these changes tested?
I've tested with a really minimal build of Arrow and Pyarrow. I don't think we want to add a build without Parquet but with Dataset and/or Acero at CI just to test this scenario.
Logs for the local build without Parquet:
The
IMPORT_LIB-NOTFOUND
has always been present and it's not new.Are there any user-facing changes?
No as this should have already been the case.