jayshrivastava commented on PR #26593: URL: https://github.com/apache/datafusion/pull/26593#issuecomment-6641595176
For https://github.com/apache/datafusion/issues/25483, I don't anticipate much changing. I think we'll need to add code related to layouts and in that implementation, we can handle bounds, similarly to to `can_interleave` and `compatible_co_partitioning_layout`. (I filed https://github.com/apache/datafusion/issues/27106 for that by the way to make sure we update those). For layouts, here's an example where we might want to account for bounds. Suppose a task has `Range(2, [10], end=20)`, and the destination has `Range(2, [20])`, we would want this behavior: ``` Source Target S0: (-inf, 10) ----+ +-------------> T0: (-inf, 20) S1: [10, 20) ------+ T1: [20, +inf) receives nothing ``` Without bounds, this could happen in theory. ``` Source Target S0: (-inf, 10) ------------------> T0: (-inf, 20) ^ S1: [10, +inf) -------------------+ | +-------------> T1: [20, +inf) ``` Since no one has really started on https://github.com/apache/datafusion/issues/25483, this is pretty speculative. I think we could find a way to ensure the desired behavior though. -- 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]
