[jira] [Resolved] (IMPALA-12883) Add support for changing the charge for a cache entry

["Joe McDonnell (Jira)" <ji...@apache.org>]

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

Joe McDonnell resolved IMPALA-12883.
------------------------------------
    Fix Version/s: Impala 4.4.0
         Assignee: Joe McDonnell
       Resolution: Fixed

> Add support for changing the charge for a cache entry
> -----------------------------------------------------
>
>                 Key: IMPALA-12883
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12883
>             Project: IMPALA
>          Issue Type: Task
>          Components: Backend
>    Affects Versions: Impala 4.4.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Major
>             Fix For: Impala 4.4.0
>
>
> The Cache implementation in be/src/util/cache currently does not support modifying the charge of a cache entry after it has been created. For cases where the size is known up front, this is fine. For example, the data cache knows the number of bytes it will consume before it creates the cache entry.
> This is a problem for caches that may not know the size of an entry up front. For example, the tuple cache may want to create a cache entry immediately to avoid concurrency issues, but then it would want to update that entry's charge as the entry is finalized (or reaches certain size increments).
> It would also be useful to expose the maximum charge allowed for a cache entry. This would allow writers to avoid creating a cache entry that is too large.



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

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