KV doesn’t currently support that
KV doesn’t currently support that
Poh I see, so the only current option is to pull all of the keys and delete them?
Mwhen running workers-rs with wrangler on local mode, my code attempts to store a value on the key value database, (no errors), but when i check the dashboard on cloudflare, there doesn't seem to actually be anything stored
Manyone know why?
CLocal mode doesn’t effect any remote resources
Mah i see
Mso if i use on my worker with local mode enabled and attempt to add something, it'll just be stored somewhere locally on my system?
COnly if you have the persist flag (wrangler 2). Otherwise it is stored in memory and is gone once dev stops
Malright, thank you
BDoes KV support secondary indexes?
INo.
IYou can list keys by prefix but that's it.
BThanks!
BSo to "resort" something I'd have to delete and readd it with a new key right? @Isaac McFadyen | YYZ01
IYeah pretty much.
BCoolio
IKeep in mind that because KV is eventually consistent if you read a value then change the value with the same key it might take up to 60s to see the new value in other locations
IIf you change the key, as long as you haven't queried the key before, it should be instant.
IIf you've queried the key before, even if it didn't exist at the time, it may take up to 60s to see the new value
BHuh... Nah, this key will have been queried before 
IIn which case, yeah, 60s (or more in very rare cases) to see in other locations.
BIt'll be queried and then immediately updated again
BFair enough, thanks!
B@Isaac McFadyen | YYZ01 do you know if there's a way to count keys? Something like the method but without returning the actual keys and just a count?
II don't believe so, no, aside from just manually calling and counting that way (which is error-prone).
BI'll have to do that then. I know that there's eventual consistency involved, but I'll need a count even if it's a rough count
IIEasy way to test, actually - if you call multiple times in a row, if the calls all take then same time then they don't get cached, if the first is slower than the rest they do get cached.
II am wrong, just tested and KV operations do indeed get cached 
ISorry about that.
BNp, thanks for checking!
BThat's more a question for the wrangler channel I think.
BThey get cached for the exact same sets of parameters. The cache key is built from the parameters (prefix, limit, or cursor) and cached for max 1 minute (IIRC you can't customize the cache TTL currently).
BDo you know if has an upper limit somehow? After 7500 keys it won't return another , but I should have inserted more keys than that 
Mthe latency on these kv gets/puts seems awfully high no?
BIt shouldn’t. If you’re doing writes concurrently then it’s possible you cached the end of the list and need to wait a minute or so. What’s your namespace?
BWhich geographic location is this happening in and are you sure the gets are happening on a key that’s supposed to be already cached? Also is this a change in behavior or a new measurement you’re looking at
MMy bad, I thought Region: Earth meant all the data was replicated globally? I’m in Australia so if both reads and writes are going somewhere off-continent that would explain these figures
MBut I am confused about why they would be going off continent?
HKV core is US/EU iirc, so writes go there. KV reads are cached locally, in the datacenter they are read from
BCorrect. https://developers.cloudflare.com/workers/learning/how-kv-works/. So yeah, writes from Australia may take a while. The first read ever for a key will be slow but subsequent reads should be fast. The reads don’t even need to be from the same data center. Anywhere in Australia will populate the cache for all of Australia.
Workers KV is a global, low-latency, key-value data store. It stores data in a small number of centralized data centers, then caches that data in …
HOh, is that new with KV2? And how do the regions work there? Is it by country?
EThe page has been there for a long time
HNo, I mean the thing where cache is applied over an entire region? The docs still seem to imply that cache is only in a single datacenter:
[M]ore popular values are cached in the data centers they are requested from.
LWhen you say "reminder that you can only list 1k at a time", do you mean that a page is only 1k max, or that all the pages can't return more than 1,000 items?
AThat one listing is limited to 1000 keys. You can use the cursor to paginate.
LAgain, I'm not 100% clear. Let's say I have 10,000 keys that match my prefix. I make an initial list() call with that prefix and I'll get back a page plus a cursor. I can use that cursor on followup list() calls to get more pages. When it's all said and done, can I get back all 10,000 keys?
AYes. First call will list 1-1000. Second call will list 1001-2000, if you specify the cursor. And so on...