Jonathan Whitaker

We have a similar use case where we'd like to assign a relation to all resources of a given type. In our platform we model something similar to AWS Permission...

> The Lookup Watch API Service will make use of the Watch and the Reachability Resolution APIs to provide a stream of updates indicating changes in the accessibility of a...

> The problem is one of scale: The API calls needed to compute the updates will differ based on resource type and permission. We could provide a batch version of...

> You'd still have to be explicit about for which types of resources, and the permissions for them, you require updates. This way, we're only computing the minimal set of...

> Should the LookupSubjectsResponse contain the path of all relations/permissions that were traversed to reach a subject? This could be very useful in building permissions panels or auditing systems. I...

@josephschorr do we want the `optional_permission` and `optional_subject` to be plural? ``` message LookupSubjectsRequest { Consistency consistency = 1; ObjectReference resource = 2; repeated string optional_permissions = 3; repeated SubjectAndRelation...

One of the large concepts behind [Google's Zanzibar](https://research.google/pubs/pub48190/) design is that you distribute the query space or access evaluation across multiple nodes when evaluating an access control decision. This enables...

Ok, so in order to get the behavior I want I'd have to reduce my batchSize (in the client config) to 1. ``` conn := &kafka.Writer{ Addr: kafka.TCP("localhost:9092"), BatchTimeout: 75...

@rhansen2 that's not how it behaves. If I do this: ``` conn := &kafka.Writer{ Addr: kafka.TCP("localhost:9092"), BatchTimeout: 75 * time.Millisecond, BatchBytes: 512, RequiredAcks: kafka.RequireAll, } ``` And then I publish...

@rhansen2 If I set BatchBytes to 512, and attempt to publish two messages - one of size 520 and one of size 2 (using the code sample above), I'd expect...