You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Todd Farmer (Jira)" <ji...@apache.org> on 2022/09/23 16:51:00 UTC

[jira] [Commented] (ARROW-14202) [C++] A more RAM-efficient top-k sink node

    [ https://issues.apache.org/jira/browse/ARROW-14202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608846#comment-17608846 ] 

Todd Farmer commented on ARROW-14202:
-------------------------------------

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 per [project policy|https://arrow.apache.org/docs/dev/developers/bug_reports.html#issue-assignment]. 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++] A more RAM-efficient top-k sink node
> ------------------------------------------
>
>                 Key: ARROW-14202
>                 URL: https://issues.apache.org/jira/browse/ARROW-14202
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>    Affects Versions: 7.0.0
>            Reporter: Alexander Ocsa
>            Assignee: Ariana Villegas
>            Priority: Major
>              Labels: query-engine
>
> Mentioned here:
> https://github.com/apache/arrow/pull/11274#pullrequestreview-768267959
> For example, a top-k implementation could periodically (when batches_ has some configurable # of rows) run through and discard data. The way it is written now it would still require me to buffer the entire dataset in memory (and/or spillover).
>  
>  



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