Bill de hÓra

> (see Improve Guidance on GET / PUT / PATCH / POST - Draft). Is this a public document or internal to Zalando?

> I suggest that we accept any content type and always return a json regardless of the representation asked by users, since this is the only representation available. If this...

@prismec thanks for raising this. This looks like a good idea at first glance; will want to think through the API signatures a bit - guessing based on the example,...

> +771 −78 1/ I want to break this pr down into smaller pieces. - name changes in tests to make room for the feature - passing the media type...

> AvroEventResource This approach seems overly keen to justify Avro for wildcard event type consumers rather than think rigorously on non-JSON representations. It puts Apache Avro into the signature space...

> A central implementation of DQL for Nakadi can greatly reduce the software/technology complexity Can you clarify what you expect from a client with a DLQ over a distributed ordered...

@ePaul thanks for reporting; let me do some digging, this one might be tricky to debug. In the meantime can you add the stream connection parameters as details?

> When Nakadi replies with an error which can't be parsed as application/problem+json, @adyach is there a bug filed against Nakadi for this? The server shouldn't be emitting junk entities.

@PetrGlad Thanks for the report - failing test cases would be useful.

> I noticed that when an InterruptedException is caught, we set the interrupt flag back using Thread.currentThread().interrupt(). Should we not also throw some exception @Dexteroo7 can you point to the...