tree 2b889d079d2a21a7ffe4e5de0daea247f0bfeb52
parent 2c4d84b1e11ae1f8857abebf7e7983e7449ff3e1
author Michael Smith <michael.smith@cloudera.com> 1709858798 -0800
committer Joe McDonnell <joemcdonnell@cloudera.com> 1710869054 +0000

IMPALA-12883: Support updating the charge on an entry in the cache

The cache implementation currently assumes that a cache
entry's charge will remain constant over time and does
not support updating the charge. This works well for
existing cache users like the data cache and codegen
cache. However, it doesn't work as well for use cases
where the final size is not known up front. Being able
to update the charge also allows for avoiding
concurrency issues where two different threads are
trying to insert the same entry.

This adds the ability to update an entry's charge after
it has been inserted into the cache. This can trigger
evictions if the size increases. This also adds a way
to retrieve the maximum charge supported by the cache.
This allows a cache user to tune its behavior to avoid
generating entries that would exceed the maximum charge.

Testing:
 - Added tests cases to the caching backend tests

Change-Id: I34f54fb3a91a77821651c25d8d3bc3a2a3945025
Reviewed-on: http://gerrit.cloudera.org:8080/21122
Reviewed-by: Michael Smith <michael.smith@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
Reviewed-by: Yida Wu <wydbaggio000@gmail.com>