[jira] [Assigned] (ARROW-16036) [C++] Substrait SinkNode Modification for usability

["Todd Farmer (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARROW-16036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Farmer reassigned ARROW-16036:
-----------------------------------

    Assignee:     (was: Vibhatha Lakmal Abeykoon)

This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

> [C++] Substrait SinkNode Modification for usability
> ---------------------------------------------------
>
>                 Key: ARROW-16036
>                 URL: https://issues.apache.org/jira/browse/ARROW-16036
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Vibhatha Lakmal Abeykoon
>            Priority: Major
>              Labels: query-engine, substrait
>
> Currently, the Substrait implementation uses a `consuming_sink` node as the end-point to capture the results of an executed query. To further enhance the ability to use the wide variety of `SinkNode`s in the streaming execution engine, it is better to evaluate other options to provide usability for various use cases. 
> Some of the use cases include consuming a Substrait query plan in R and Python APIs. And this extends beyond the Arrow APIs where third-party tools willing to use Substrait can be benefitted from these. At the moment there is active work on providing R/Python APIs for Substrait consumption (https://issues.apache.org/jira/browse/ARROW-15779). 
> A potential modification to provide usability is to take in a `SinkNodeFactory`-like interface instead of just using the `ConsumingSink` (current implementation). Such a modification would provide flexibility in developing a wide array of applications. 
> This issue is open for discussion. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)