https://authzed.com logo
Join Discord
Powered by
"spicedb, rebuild the cache now, with these last ...
# spicedb
j
> "spicedb, rebuild the cache now, with these last changes" this is essentially what the ZedToken encodes
e
Hummm, so if I perform a check after a write passing the zedtoken, I will have a fresh cache, and for the next checks, I won't need to pass a zedtoken? I didn't find "quantization window" in the documentation, do you have a link?
j
if you want it to reflect that write, you still need to pass a zedtoken
we don't recommend people changing the quantization window/period without a good reason
its an implementation detail and can change over time
the point is: if you need fully consistent checks, you need to either request that all time (using that consistency level) or pass a zedtoken
otherwise, if you do not care about some staleness nor the New Enemy Problem, you can just always make a 
minimize_latency
call without a zedtoken
I should say if you want to guarantee it reflects that write
e
For me, wouldn't be a problem if I need to wait for 5s (for example), to the write operation be propagated and I be able to get the right result in a check permission.
j
if you don't care if it takes a few seconds, then no need
then you have no need to keep zedtokens
but it does open you up to the New Enemy Problem
so you need to be aware of that
e
yeah .. I know ...
j
so long as you are aware, then yeah, its perfectly fine
plenty of users don't particularly care
e
So, to confirm, if I don't use a token, will I get a consistent check result after ~5s? The token is only to solve the consistency between these few seconds.
j
yes, so long as you don't change the defaults
e
Thank you @Joey !
j
of course
PreviousNext
Powered by