R.I.Pienaar

Results 138 issues of R.I.Pienaar

### Proposed change Since introducing Direct Get we lost our, admittedly imperfect, read-after-write consistency in KV stores. We felt then that was an acceptable behaviour change but its clear that...

accepted
proposal
needs info
2.12+
needs design
request-from-customer

### Proposed change It's a frequently requested feature to allow messages to be delivered on a schedule or to support delayed publishing. We propose here a feature where 1 message...

accepted
proposal
2.12+

### Proposed change Distributed counters is a very important principal to have as a distributed systems developer and we are uniquely positioned to build very large globally distributed counters given...

accepted
proposal
2.12+
needs design

### Proposed change We need to formalise how a Mirror becomes the primary in a pair of streams. Today we do not support removing the Mirror configuration from a stream,...

proposal
2.12+
needs design

### Proposed change We need to support batch publishes for a few use cases: * Clients want a very high ingest rate on streams and so might want to send...

proposal
2.12+
needs design

### Proposed change On the back of success with Auth Callouts we should look at a framework for generic callouts to be placed in various other scenarios: * Place a...

stale
proposal
2.12+
needs design
stretch

### Proposed change The server should have a `map[string]string` block in it's configuration for metadata that is queryable via Z endpoints. ### Use case This will allow monitoring tools to...

accepted
proposal
2.12+
easy

### Proposed change Today when receiving JSON fields in API requests that have invalid flags we accept them but log about it. These requests should be rejected. See ADR-44 ###...

accepted
proposal
2.12+
easy

### Proposed change Today we see cases where if the logging output device blocks the entire server blocks since we are working on the assumption that logging always works and...

stale
accepted
proposal
2.12+