Is your feature request related to a problem or challenge?
The API health policy deprecation guidelines say deprecated APIs remain for
6 major versions or 6 months, whichever is longer
main is at 55.0.0, so the next release is 56.0.0 and anything deprecated in 50.0.0 or earlier can now be removed.
These eight are independent one-offs, each a few lines in a different crate:
Describe the solution you'd like
Remove all eight items and supporting code
These are independent, so this can be done as one PR or several -- feel free to pick off whichever items you like.
- While this is a breaking Rust API change, the PR should carry the
api change label
- DO NOT add a note to the
56.0.0 upgrade guide, as removing deprecated APIs is clear and the compiler has guided people off them in the past
Describe alternatives you've considered
N/A
Additional context
Follow on to #23080, which did the same sweep at the 49.0.0 cutoff, and #24535.
Is your feature request related to a problem or challenge?
The API health policy deprecation guidelines say deprecated APIs remain for
mainis at55.0.0, so the next release is56.0.0and anything deprecated in50.0.0or earlier can now be removed.These eight are independent one-offs, each a few lines in a different crate:
ScalarValue::raw_datato_arrayget_statistics_with_limitget_files_with_limitandcompute_all_files_statisticsDisplayableExecutionPlan::to_stringifiedindentortree_renderExprSimplifier::simplify_with_cycle_countsimplify_with_cycle_count_transformedDynEq/DynHashre-exportdatafusion_expr_common::dyn_eqExecutionProps::start_executionmark_start_executionUserDefinedFunctionPlannerUnicodeFunctionPlannerandDateTimeFunctionPlannerNow::newnew_with_configDescribe the solution you'd like
Remove all eight items and supporting code
These are independent, so this can be done as one PR or several -- feel free to pick off whichever items you like.
api changelabel56.0.0upgrade guide, as removing deprecated APIs is clear and the compiler has guided people off them in the pastDescribe alternatives you've considered
N/A
Additional context
Follow on to #23080, which did the same sweep at the
49.0.0cutoff, and #24535.