Feature Request P2
Status Update
Comments
jo...@google.com <jo...@google.com>
[Deleted User] <[Deleted User]> #2
Are there currently any plans around this feature? We have a situation where we are storing objects in memcache with unknown key names (that is they are generated and there are an unknown number). At present there is no way to remove all of these objects without somehow keeping track of the key names. A means to remove all objects in a given namespace would solve this issue.
eo...@google.com <eo...@google.com> #4
One way to effectively delete all items in a namespace is to change the name of the namespace.
So for example you could include a "generation count" as part of the namespace name, then when you wanted to delete all items in the namespace you would simply increment the generation count.
The items in the old namespace will gradually be evicted as you use the new namespace.
So for example you could include a "generation count" as part of the namespace name, then when you wanted to delete all items in the namespace you would simply increment the generation count.
The items in the old namespace will gradually be evicted as you use the new namespace.
ss...@eecworld.com <ss...@eecworld.com> #5
Mind blown! Elegant and brilliant! Add the "generation" technique to the docs and in my book, you can cross "flush memcache by namespace" off the desired features list.
ss...@eecworld.com <ss...@eecworld.com> #6
#5190 also touches on a similar issue.
is...@google.com <is...@google.com>
la...@conductorio.com <la...@conductorio.com> #7
I'd like to also voice a desire for the ability target multiple objects for a given namespace (without knowing the objects' keys). I have several hundred thousand objects in memcache, each namespaced to a customer account (i.e.many objects per namespace). These objects are retained for as a long as possible (i.e. they may never expire.). But periodically we may need to flushed/invalidate objects for a specific account (perhaps they are no longer a customer; perhaps the cached data no longer reflects the truth, etc), As it stands, there is no way to achieve this without also flushing other customers' data. Perhaps I'm "holding it wrong", but I would concur with the OP (8 years later!) that this omission of functionality results in a product/feature that feels partially incomplete (severely handicapped).
Description
right now it seems like a half implementation if because i can only get/add/delete single objects by namespace.