yetitwo
06/01/2022, 4:30 PMminimize_latency
works, and I realized that I'm not actually sure when and how SpiceDB would do the work of going to the datastore and recomputing a particular subproblem if you've got minimize_latency
selected. (it's obvious to me for both at_least_as_fresh
and fully_consistent
- it's looking at the zedtoken and discarding any results that are less than the specified revision)yetitwo
06/01/2022, 4:30 PMminimize_latency
is discouraged?Joey
06/01/2022, 4:31 PMJoey
06/01/2022, 4:31 PMminimize_latency
is encouragedJoey
06/01/2022, 4:32 PMat_least_as_fresh
(most callers can just use minimize_latency
)Joey
06/01/2022, 4:35 PMminimize_latency
works is: SpiceDB will choose a revision from the database within a quantization window (default: 5s + some additional leeway) and then use that revision for the request. so long as the caches are at least as new as that revision, they are usedJoey
06/01/2022, 4:35 PMat_least_as_fresh
just specifies that minimum revision directlyJoey
06/01/2022, 4:37 PM--datastore-revision-quantization-interval
controls the 5s
Joey
06/01/2022, 4:38 PMminimize_latency
(or just don't specify anything, since its the default) you're telling SpiceDB to pick a revision that is most likely to already be cached, without any other hard requirementsJoey
06/01/2022, 4:38 PMat_least_as_fresh
with a ZedToken (which has a revision ID encoded), you are saying "the cache must contain at least this revision to be used"Joey
06/01/2022, 4:39 PMfully_consistent
is "pick the latest revision from the database and use it"yetitwo
06/01/2022, 4:41 PMAlex
06/01/2022, 5:11 PMJoey
06/01/2022, 5:16 PMAlex
06/01/2022, 5:19 PMJoey
06/01/2022, 5:20 PMJoey
06/01/2022, 5:20 PMJoey
06/01/2022, 5:21 PMdocumentX-to-billing
Joey
06/01/2022, 5:21 PMdocumentX
be shared by alice-to-billing
Joey
06/01/2022, 5:21 PMAlex
06/01/2022, 5:25 PMJoey
06/01/2022, 5:25 PMJoey
06/01/2022, 5:26 PMJoey
06/01/2022, 5:26 PMAlex
06/01/2022, 5:26 PMJoey
06/01/2022, 5:27 PM+1
and use case in the issueJake
06/01/2022, 5:58 PMJake
06/01/2022, 5:59 PMAlex
06/01/2022, 6:10 PMAlex
06/01/2022, 6:47 PM