-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explicitly mark parquet for tests in datafusion-common #8497
Explicitly mark parquet for tests in datafusion-common #8497
Conversation
@alamb, I would appreciate it if you could review this PR to ensure it aligns with our expectations. |
Thank you @Dennis40816 -- this looks like a good change and is what I would expect. I have started the CI for this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @Dennis40816 -- I have just one small request and I think this PR will be good to go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Dennis40816 !
cc @jayzhan211
The CI check seems to be great: https://github.com/apache/arrow-datafusion/actions/runs/7180238066/job/19571832278?pr=8497 |
Thanks again @Dennis40816 |
Thanks @Dennis40816 ! |
Which issue does this PR close?
Closes #8250.
Rationale for this change
What changes are included in this PR?
In the tests for
datafusion-common
, mark the test programs that require parquet for compilation with#[cfg(feature = "parquet")]
. Additionally, in the CI, add a check to verify whetherdatafusion-common
can compile without any features enabled (bycargo check
).Are these changes tested?
Running
cargo test --tests --no-default-features -p datafusion-common
.The result is a pass.
Are there any user-facing changes?