tustvold edited a comment on pull request #1526:
URL: 
https://github.com/apache/arrow-datafusion/pull/1526#issuecomment-1010171638


   > Maybe a wrapper over the stream could achieve the goal
   
   My instinct would be to suggest having the shared ref internal to the stream 
implementation, instead of a wrapper. Otherwise I suspect you will run into 
borrow checker, pinning, and async pain. This would also avoid needing to make 
breaking changes to SendableRecordBatchStream?
   
   Another thing to potentially think about is that many of the operators 
aren't actually streams, rather they spawn a tokio task and then return an mpsc 
queue. There will need to be some accounting of both data buffered in the 
queue, and data in the operators "task". My gut feeling is this is going to 
require adding some sort of RAII tracking field to `RecordBatch` or possibly 
`Buffer` but I'm not really sure...


-- 
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]


Reply via email to