Skip to content

Conversation

@alamb
Copy link
Contributor

@alamb alamb commented Oct 31, 2025

Which issue does this PR close?

Rationale for this change

While working on #8754 I found the current formulation a bit akward so let's fix that

What changes are included in this PR?

Move the builder configuration to a trait so the tests read more fluently.

This is totally unecessary, it just makes me feel better about the tests

Are these changes tested?

Yes by CI

Are there any user-facing changes?

No this is test only

@github-actions github-actions bot added the parquet Changes to the parquet crate label Oct 31, 2025
let test = ParquetPredicateCacheTest::new().with_expected_records_read_from_cache(49);
let async_builder = test.async_builder().await;
let async_builder = test.add_project_ab_and_filter_b(async_builder);
let async_builder = test.async_builder().await.add_project_ab_and_filter_b();
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the key change -- move the logic to add specific filters to an extension trait rather than a methog on the ParquetPredicateCacheTest test fixture

@alamb alamb force-pushed the alamb/rewrite_tests2 branch from 185af9f to fbfc545 Compare November 1, 2025 10:30
.unwrap()
}

/// Return a [`ParquetRecordBatchReaderBuilder`] for reading the file with
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this code was moved to a new trait -- but the logic is the same

@alamb alamb marked this pull request as ready for review November 1, 2025 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

parquet Changes to the parquet crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant