Complete physical execution planning of range partitioning

[saadtajwar]

Is your feature request related to a problem or challenge?

This issue is for subsequent passes on the physical execution planning of the newly-supported range partitioning, specifically for support of functions try_swapping_with_projection, try_pushdown_sort, repartitioned - follow up from #23137 , part of #22395

Describe the solution you'd like

For try_swapping_with_projection, try_pushdown_sort, and repartitioned - see if these passes on the physical plan are able to be supported for Range partitioning, and if so implement them accordingly

Describe alternatives you've considered

If not able to support for Range partitioning, keep the default return values and remove the TODO comments (or leave a comment as to why they cannot be implemented for Range partitioning)

Additional context

N/A

[saadtajwar]

take

[gabotechs]

Hi @saadtajwar, I see this issue was created a couple of weeks ago with still a TODO description.

As it has not received updates, I assume it's stale and we can close it? otherwise feel free to update the issue following our template guidelines if it's in fact still active.

[saadtajwar]

Hi @saadtajwar, I see this issue was created a couple of weeks ago with still a TODO description.

As it has not received updates, I assume it's stale and we can close it? otherwise feel free to update the issue following our template guidelines if it's in fact still active.

Hey @gabotechs , apologies for the delay in updating this issue - I believe we still want to tackle this one, I'll update the description to accurately reflect the work encompassed here! Will have that done by EOD today :) Thanks!

[gabotechs]

awesome, thanks @saadtajwar!

[saadtajwar]

@gabotechs - updated this, hopefully this is more clear now! I should be able to start working on the implementation later this afternoon :)

[saadtajwar]

@gene-bordegaray & @gabotechs - have a PR up for this at #23617 ! 🚀