You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/10/02 00:56:00 UTC

[jira] [Updated] (IMPALA-4836) Kudu scans should operate within a memory constraint

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

Tim Armstrong updated IMPALA-4836:
----------------------------------
    Priority: Minor  (was: Major)

> Kudu scans should operate within a memory constraint
> ----------------------------------------------------
>
>                 Key: IMPALA-4836
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4836
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 2.9.0
>            Reporter: Tim Armstrong
>            Priority: Minor
>              Labels: kudu, resource-management
>
> It is somewhat unclear how we will do this, given that Kudu does its own memory management outside of our buffer pool.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org