I somehow understand it needs time to fix it, but shouldn't WE have a test period for this kind of t
I somehow understand it needs time to fix it, but shouldn't WE have a test period for this kind of things?
JI'd have to look at how I've done it before but my knee jerk (from my phone) reaction without looking is probably timestamp in the Metadata, maybe something like this
TAhh, sure! Thank you! That will do it
MIn case you missed it — here's the details on the latest Workers KV performance improvements that just shipped! https://blog.cloudflare.com/faster-workers-kv/ @Workers KV
The Cloudflare Blog
Today, we’re announcing up to 3x faster KV hot reads, with all KV operations faster by up to 20ms. And we want to pull back the curtain and show you how we did it.
AWow!
Thats a massive gain!
Thats a massive gain!
Dthat's huge! very nice!
DThank you!
TWe're super excited for this ship, and we're going to continue to make KV super fast for your data globally. The details of how we did it are all in the blog, but the graphs really show the impact 
BIn the kv docs /getting-started
I can't get this command to work:
npx wrangler kv key put --binding=<BINDING_NAME> "<KEY>" "<VALUE>"
just trying to follow the kv-tutorial
I used kv_binding_name - trying to follow the docs.
Though the docs say: name it BINDING_NAME - the very next step shows a create command with kv_binding_name
✘ [ERROR] A namespace with binding name "kv_binding_name" was not found in the configured "kv_namespaces".
✘ [ERROR] A namespace with binding name "kv-tutorial-kv_binding_name" was not found in the configured "kv_namespaces".
I can't get this command to work:
npx wrangler kv key put --binding=<BINDING_NAME> "<KEY>" "<VALUE>"
just trying to follow the kv-tutorial
I used kv_binding_name - trying to follow the docs.
Though the docs say: name it BINDING_NAME - the very next step shows a create command with kv_binding_name
✘ [ERROR] A namespace with binding name "kv_binding_name" was not found in the configured "kv_namespaces".
✘ [ERROR] A namespace with binding name "kv-tutorial-kv_binding_name" was not found in the configured "kv_namespaces".
BIt does work with the ID - but, I'm just reporting broken documentation continuity.
Jhelp I am trying to import kv to my javascript worker with
import { KVNameSpace } from '@cloudflare/kv-name-space'
Tit doesn;t work@JamieD132 What is the error you're getting and what do you expect to get?
T
KHi guys! The documentation is a little murky on this one, how do I specify the expiration on the KV PUT REST body? https://developers.cloudflare.com/api/operations/workers-kv-namespace-write-key-value-pair-with-metadata
Interact with Cloudflare's products and services via the Cloudflare API
MOoh yeah they should have an example body there, for sure. I assume it's the same as the
wrangler kv bulk putwas that a suggestion from an AI tool? that's my best guess :D anyway, follow https://developers.cloudflare.com/kv/get-started/#3-bind-your-worker-to-your-kv-namespace and https://developers.cloudflare.com/kv/get-started/#5-access-your-kv-namespace-from-your-worker to use a KV namespace with a worker
TThanks for flagging! let me verify
T@kindaraffy yes, expiration is supported in the REST API, we'll be fix that in docs
You can specify expiration or expirationTtl as a query param
So I can tell the users: https://api.cloudflare.com/client/v4
/accounts/{account_id}/storage/kv/namespaces/{namespace_id}/values/{key_name}?expiration=<secondsSinceEpoch>
or https://api.cloudflare.com/client/v4
/accounts/{account_id}/storage/kv/namespaces/{namespace_id}/values/{key_name}?expirationTtl=<secondsFromNow>
You can specify expiration or expirationTtl as a query param
So I can tell the users: https://api.cloudflare.com/client/v4
/accounts/{account_id}/storage/kv/namespaces/{namespace_id}/values/{key_name}?expiration=<secondsSinceEpoch>
or https://api.cloudflare.com/client/v4
/accounts/{account_id}/storage/kv/namespaces/{namespace_id}/values/{key_name}?expirationTtl=<secondsFromNow>
KThank you.
CHey! Are there documented (or undocumented) rate limits on number of writes to different KV keys from a worker (on the paid plan)? We are seeing 429s when we try to write a few thousand keys within a few seconds.
TKV has 1 write per second per key limit from the binding https://developers.cloudflare.com/kv/platform/limits/ and the APIs have global rate limits https://developers.cloudflare.com/fundamentals/api/reference/limits/#:~:text=The%20global%20rate%20limit%20for,receiving%20a%20HTTP%20429%20response.
CDo the api rate limits apply to calls made from a worker binding?
CWe are writing to different keys, so the 1 per second should not apply
TDM'd
IRelated to the new upcoming cache purging changes, couldn't these also apply to KV?
https://blog.cloudflare.com/instant-purge/
Is it generally possible to purge a specific KV key? I think if a KV value is locally cached, and you update this it could in theory especially with the new purging system 'instantly' purge all regional KV caches right? Think this could bring quite some benefits to keep KV reads latency.
E.g. I need super quick access to a 'configuration' stored in KV, this 'configuration' is updated at most a couple of times a day. If we can keep this in the cache until this value is updated or deleted, it would speed up calls to KV a lot. Currently it's documented that KV updates do not purge KV caches, in this case it would be great if it did!
https://blog.cloudflare.com/instant-purge/
Is it generally possible to purge a specific KV key? I think if a KV value is locally cached, and you update this it could in theory especially with the new purging system 'instantly' purge all regional KV caches right? Think this could bring quite some benefits to keep KV reads latency.
E.g. I need super quick access to a 'configuration' stored in KV, this 'configuration' is updated at most a couple of times a day. If we can keep this in the cache until this value is updated or deleted, it would speed up calls to KV a lot. Currently it's documented that KV updates do not purge KV caches, in this case it would be great if it did!
TThanks for the feedback @ItsWendell, like you mentioned, KV doesn't have cache purges but it's something we're keeping our eyes on
Wcan we use https://github.com/cloudflare/cloudflare-typescript with local wrangler created kv namespace ?
GitHub
The official Typescript library for the Cloudflare API - cloudflare/cloudflare-typescript
HNo, since it does not expose an HTTP API
Wohh, got it, thanks
Ti am guessing maybe DB is more suitable for production level deployment for permissions? to ensure consistency.
IThe "inconsistency" of KV would just mean that an update might take 60 seconds to propogate globally. If you're OK with 60-second delays when adding or removing permissions then KV would still be suitable, but if not then KV isn't for you.
Tyes, I did assume permissions are usually crucial for production environment best with zero latency and 100% consistency.
what about D1? that said, I actually stick to D1 for auth data for my development project... simply because D1 offers more free allowances.
what about D1? that said, I actually stick to D1 for auth data for my development project... simply because D1 offers more free allowances.
ID1 is single-region currently, so while you'd get consistency there you're definitely not going to get zero latency.
IIn general there's no such thing as zero-latency, 100% consistency - all databases are just trading one for the other, some fully (i.e. KV prioritizes speed, D1 prioritizes consistency) and some partially (i.e. in etcd you can choose to read possibly-stale values or consistent values and your app can make that choice itself)
APermissions doesn't change often. Firebase auth token cache auth tokens upto 1 hr by default. 60sec doesn't seems to be problem.
IYeah IMO 60 seconds is perfectly OK for permission use-cases. Even if you need to revoke permissions from a user quickly because of an issue, 60 seconds is very quick and won't give them much time to do anything dangerous.
IYou can also implement it as a tiered system: for most permission requests you can check KV, but then if there's something extremely sensitive (like billing details or a purchase or something) you can go back to a central DB that is consistent.
JHello!
Have way to use KV in local dev env? or an emulator?
Have way to use KV in local dev env? or an emulator?
HWrangler can emulate KV in a Worker for you
JI'm running a worker locally (
wrangler devwrangler kv key put ... --local <key> <value> but my <kvnamespace>.get in my worker always returns null. I tried listing them from the worker too, and there's no keys at all. Listing them with "kv key list --local" tells me they are there. I can also read them with kv key get. Any suggestions on where I should start to dig to figure it out?JAny example to use KV with Typescript? All examples I see, have bugs =/
JJWhat I did wrong?
Try to use Cloudflare KV, in
Try to use Cloudflare KV, in
npm run preview and in deploy, get some error: Error adding key-value pair: Error: Error adding key-value pair: ReferenceError: env is not definedexport const runtime = 'edge';
export const putKV = async (key, value) => {
try {
await env.KV_PREVIEW.put(key, value);
return;
} catch (error) {
throw new Error(Error adding key-value pair: ${error});
}
};
WHow are you invoking putKV
WAnd where is env coming from there
W(May be better to ask in #next-on-pages )
J@Walshy | Deploying I dont know how to make this with TypeScript, try a lot of examples and tutorials.
But, I change to Node.JS standard code, and work.
In loca env: pass, not generate error but, not save in KVS.
Only work 100% in CF Worker.
But, I change to Node.JS standard code, and work.
In loca env: pass, not generate error but, not save in KVS.
Only work 100% in CF Worker.
THey folks, in reference to the above inaccurate metrics and free tier quota exhaustion, this fix has now been rolled out!
MHi, running into some weird eventual consistency behavior with KV - when updating a KV key value pair (via the API), accessing it via worker seemingly randomly returns the old version and switches back and forth to the new updated one. Any ideas? cacheTtl used to be set to 5 minutes, but this issue has been apparently occurring for the past 24 hours
Mwhen looking at the KV dashboard, the correct version is present there, but workers still return the old version, even after several hours
