This will shield implementations from having to deal with SinkNodeConsumer. The implementation should be pretty similar to the SinkNode that we have today for exec plans. We can use a PushGenerator to be our producer/consumer queue that the RecordBatchReader consumes. The Substrait sink consumer will then push into that PushGenerator. This method would fail if the plan has more than one top-level relation (e.g. more than one sink).
Reporter: Weston Pace / @westonpace
Note: This issue was originally created as ARROW-15849. Please see the migration documentation for further details.
This will shield implementations from having to deal with SinkNodeConsumer. The implementation should be pretty similar to the SinkNode that we have today for exec plans. We can use a PushGenerator to be our producer/consumer queue that the RecordBatchReader consumes. The Substrait sink consumer will then push into that PushGenerator. This method would fail if the plan has more than one top-level relation (e.g. more than one sink).
Reporter: Weston Pace / @westonpace
Note: This issue was originally created as ARROW-15849. Please see the migration documentation for further details.