[asterisk-bugs] [JIRA] (ASTERISK-28942) res_sorcery_memory_cache: Individual object expiration behaves unexpectedly with full backend caching

[Friendly Automation (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251170#comment-251170 ] 

Friendly Automation commented on ASTERISK-28942:
------------------------------------------------

Change 14540 merged by Friendly Automation:
res_sorcery_memory_cache: Disallow per-object expire with full backend.

[https://gerrit.asterisk.org/c/asterisk/+/14540|https://gerrit.asterisk.org/c/asterisk/+/14540]

> res_sorcery_memory_cache: Individual object expiration behaves unexpectedly with full backend caching
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28942
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28942
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_sorcery_memory_cache
>    Affects Versions: 13.33.0, 16.10.0, 17.4.0
>            Reporter: Joshua C. Colp
>            Assignee: Joshua C. Colp
>
> When expiring an individual object over AMI or the CLI in the sorcery memory cache it is expected that the object will be updated soon after. With full backend caching this does not occur and instead the object remains removed until a full backend update occurs. This is behavior which can be unexpected for some people.



--
This message was sent by Atlassian JIRA
(v6.2#6252)