Follow-up to #24074, per @alamb's suggestion.
#24074 introduced PruningPredicateBuilder (.with_file_schema(...), .with_error_counter(...), .with_max_in_list_size(...), .build(...)/.try_build(...)) as the extensible entry point for constructing a PruningPredicate.
As a follow-up we should:
- Point people at
PruningPredicateBuilder from the PruningPredicate::try_new doc comment.
- Deprecate
PruningPredicate::try_new (#[deprecated]) and migrate its call sites to the builder.
- Move the construction logic into the builder so there is a single place to add future parameters.
Non-blocking cleanup — no behavior change.
Follow-up to #24074, per @alamb's suggestion.
#24074 introduced
PruningPredicateBuilder(.with_file_schema(...),.with_error_counter(...),.with_max_in_list_size(...),.build(...)/.try_build(...)) as the extensible entry point for constructing aPruningPredicate.As a follow-up we should:
PruningPredicateBuilderfrom thePruningPredicate::try_newdoc comment.PruningPredicate::try_new(#[deprecated]) and migrate its call sites to the builder.Non-blocking cleanup — no behavior change.