]> git.ipfire.org Git - thirdparty/asterisk.git/commit
res_sorcery_memory_cache: Disallow per-object expire with full backend.
authorJoshua C. Colp <jcolp@sangoma.com>
Wed, 10 Jun 2020 09:35:50 +0000 (06:35 -0300)
committerFriendly Automation <jenkins2@gerrit.asterisk.org>
Thu, 18 Jun 2020 23:02:11 +0000 (18:02 -0500)
commit419be230031b2ef1474da8e296f9b8e967075f6a
tree6f09b56fb02711420fbf35bba3394d649879b5af
parent63c82caebc4cab01f7e51850e8adeec991e95a2e
res_sorcery_memory_cache: Disallow per-object expire with full backend.

The AMI action and CLI command did not take into account the properties
of full backend caching. This resulted in an expired object remaining
removed until a full backend update occurred, instead of having the
object updated when needed.

This change makes it so that the AMI action and CLI command for object
expire will now fail instead of putting the cache into an undesired
state. If full backend caching is enabled then only operations
which act on the entire cache are available.

ASTERISK-28942

Change-Id: Id662d888f177ab566c8e802ad583083b742d21f4
doc/CHANGES-staging/sorcery_memory_cache_full_expire_object.txt [new file with mode: 0644]
res/res_sorcery_memory_cache.c