]> 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 22:56:17 +0000 (17:56 -0500)
commit1a40a6d55a0909d4a90f7430b1aefcbfa306407a
treef4db6b99e40ab04d45333a63905ed9fef6d1ca18
parent8576603fafa60b93feca5838cf67efa2fa925372
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