nakadi
nakadi copied to clipboard
zalando
A distributed event bus that implements a RESTful API abstraction on top of Kafka-like queues
When making a request to an upstream authorization server, the API returns 400 instead of indicating an authorization issue. The response structure is also incorrect - the API definition defines...
The documentation does not specify what's the meaning of this field. It seems that the original idea was for this field to hold the name of the event type, but...
when you create a subscription with specific cursors, you don't see any stats for this subscription (and the partitions) until you start consuming the subscription. For better user feedback it...
It would be great to have both in streaming API and in subscription API in addition to existing query parameters new param **max_uncommited_events_per_partition** As an example assume the following scenario:...
# One-line summary Remove partition count logic that depended on messagePerMinute and messageSize from default statistics
Docker compose doesn't need env arguments anymore
# One-line summary Provide error response code 406 (NOT ACCEPTABLE) when trying to read JSON event type with `application/avro-binary` header.
# One-line summary Mention that event_stream.read|write scopes are not used > Zalando ticket : – ## Description This adds two lines to the API definition indicating that the nakadi.event_stream.read|write scopes...
# One-line summary > Zalando ticket : 1622 ## Description Add ability to specify timeout when using publishing apis and is taken from custom header `X-TIMEOUT`. - This ability will...
## Description This changes logging backend from `log4j` (1.x) to `log4j2`: * most of sub-projects are changed to use `org.slf4j:slf4j-api` only, instead of specific `org.slf4j:slf4j-log4j12` * removed `log4j.properties` for some...
