alamb commented on PR #23231: URL: https://github.com/apache/datafusion/pull/23231#issuecomment-4859795587
> I agree panics are not good and to keep the existing `not_impl_err()`s but for this specific PR are we agreeing that it is best to not introduce this until DF can explicitly make a decision like with CBO as mentioned or a user has a need for this so we can better understand the use case before implementing? One question I would have is: 1. What type of query would produce a range repartitioning? Can we write such a think in SQL today? I can envision it being used when one side of a join is unpartitioned and one side is range partitioned -- the optimizer would have to put a range repartition to match up the keys If that is the case, adding range repartitioning in preparation seems ok to me -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
