[GitHub] [arrow-datafusion] crepererum commented on issue #5278: Strange Behaviour on RepartitionExec with CoalescePartitionsExec.

["crepererum (via GitHub)" <gi...@apache.org>]

crepererum commented on issue #5278:
URL: https://github.com/apache/arrow-datafusion/issues/5278#issuecomment-1429904075

   Having a quick look an the plan: the repartition will partition into a single partition (because you only have a single unique key) which is likely not the first partition. The stream for the first partition will only advance when `RepartitionExec` either gets an element that is hashed into it (never in your case) or when the input terminates. However I don't understand why this is an issue here, because `CoalescePartitionsExec` polls all streams/partitions in parallel. So there's indeed some bug here.


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org