pulsar-client-reactive
pulsar-client-reactive copied to clipboard
apache
Reactive client for Apache Pulsar
The current adapter implementation wraps the Java client and throws the errors what the Java client throws. Since the goal is to design a stable API which could be implemented...
https://github.com/apache/pulsar-client-reactive/actions/runs/3641666977/jobs/6148015937#step:4:578
https://github.com/apache/pulsar-client-reactive/actions/runs/3641666977/jobs/6147937156#step:4:539 ``` org.apache.pulsar.reactive.client.api.ReactiveMessagePipelineTest maxInflight(int) Test [1] 1 FAILED (5.5s) org.opentest4j.AssertionFailedError: Expecting value to be true but was false at app//org.apache.pulsar.reactive.client.api.ReactiveMessagePipelineTest.maxInflight(ReactiveMessagePipelineTest.java:321) ```
It would be nice to add BlockHound tests to check that we're not blocking accidentally.
see https://github.com/apache/pulsar-client-reactive/pull/29/files#r1033304281 It would be useful to refer to ReactiveMessageReaderBuilder#endOfStreamAction in the documentation for these methods. When endOfStreamAction == EndOfStreamAction#COMPLETE, readOne will return an empty Mono if the reader reaches...
Related to https://github.com/apache/pulsar-client-reactive/pull/28/files#r1033276692 The way the backpressure solution works is that InflightLimiter will never create more demand with ReactiveStreams subscription requests than the configured limit. This is a bit hard...
related to review comment https://github.com/apache/pulsar-client-reactive/pull/28/files#r1033269354 It is necessary to explain ReactiveMessageSenderCache and that it's necessary for production usage to get proper performance.