https://discord.cloudflare.com logo
Join Discord
Powered by
# kv
  • j
    Anyone know a method to clear out all keys in a namespace using the api without listing them and looping or using bulk delete or delete/recreating the namespace?
  • j
    Hmm, maybe I can just put a month long expiration on everything instead so old/unused keys just fall out automatically.
  • v
    That's currently the best mechanism if that works for you.
  • a
    Beware expiration is from when you write. It does not refresh on read. So a key can be read a lot and still expire once the TTL is over.
  • j
    Yeah, the idea was to run my updates once a month, but I just ended up writing the code to remove the old keys instead. Probably better I don't end up where I forget to run it, go on vacation and then all the keys go poof. Ha!
  • t
    Small bug report: the name of a KV namespace on the website uses default input styling
  • a
    Could you please share a screenshot of what you mean by this?
  • t
    (yes, that input field is not censored, that's just the way it is)

    https://cdn.discordapp.com/attachments/874727019479437372/1111225161530748968/Screenshot_2023-05-25_at_11.30.12.png▾

  • v
    Are you saying because it's got a black background in the dark theme? Or because it's non-obvious that it's editable?
  • t
    it's style doesn't fit the rest of the page
  • t
    it literally just is an 
    <input>
    with 
    background-color: #000
  • t
    IMO, that 
    Namespace Name
    field should look like the input for 
    Key
  • b
    Is there a way to list keys from KV in reverse?
  • b
    As far as I understand it, KV orders keys in ascending order lexicographically righ?
  • b
    Is there a way to get the "top 10" keys or something?
  • d
    you familiar with postma?
  • d
    postman*
  • d
    id check documentation there if anything /shrug
  • u
    Not currently sadly
  • b
    Ah, okay. I'll have to store my keys in reverse then
  • u
    #773219443911819284 do support reverse sort and you could add cache api on top of DOs which would make it somewhat close to KV
  • b
    Thanks
  • b
    So I have a problem, I write data to KV (via a CF worker), then in another request (to a CF worker) I 
    list
    keys then run 
    get
    on those keys. My problem is that 
    get
    returns 
    null
    if I 
    get
    those keys too quickly (after the write request)... What is the proper solution here? I'm thinking of writing a 
    while
    loop that keeps `get`ing those keys until KV returns something other than 
    null
    ?
  • j
    This is really by design with the way that KV's eventual consistency model works: https://developers.cloudflare.com/workers/learning/how-kv-works/
  • j
    You could do a 
    while
    loop, but it really sounds like you want more durable storage, so something like Durable Objects would likely be better suited: https://developers.cloudflare.com/workers/learning/using-durable-objects/
  • b
    Thanks!
  • u
    That is interesting that the list shows it though on first get it shouldn’t be cached. Unless you tried to do a get before the list then get 🤔
  • b
    Yeah, Idk what's going on
  • b
    What I've decided to do was store the creation date in the key metadata, and wait 60 seconds after it's created (if I'm trying to get the value before that time)
  • b
    I tried using lower values like 30 seconds, etc, but I was still getting nulls. It seems like 60 seconds is how long I should wait before I can confidently not get a null value