Re: [I] Add `return_empty_batch` flag to `LimitedBatchCoalescer` [datafusion]

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

2010YOUY01 commented on issue #18859:
URL: https://github.com/apache/datafusion/issues/18859#issuecomment-3604724883

   I vaguely recall the root cause of this edge case: when dataframe.collect() polls the plan root and gets no output, the root node is expected to produce an empty batch. That’s why this hack shows up in multiple places.
   
   A cleaner approach would be for the DataFrame layer to construct an empty batch when collect() returns nothing, so we don’t need to special-case this behavior throughout the codebase.


-- 
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@datafusion.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscribe@datafusion.apache.org
For additional commands, e-mail: github-help@datafusion.apache.org