Paolo Patierno
Paolo Patierno
The current implementation just "detaches" the AMQP consumer link when there are no partitions available for consuming. It's not the right Kafka semantics where the client is just idle without...
The AMQP bridge starts and HTTP server for health checks replying on `/health` and `/ready` for liveness and readiness probes. The current Deployment description (using fabric8 maven plugin) is using...
Currently the message key is specified through the custom annotation : x-opt-bridge.key We could use the system property group-id for that. Leaving the x-opt-bridge.partition custom annotation for specifying partition. So...
Considering the current AMQP proposal on topic/subscriptions ... https://github.com/grs/amqp_subscriptions/ The groupid currently identified in the address [topic]/group.id/[groupid], could be specified with the link name. It's something like the subscription name...
When an AMQP sender attaches a link in order to send message to the bridge, it could be interesting to use the attach "properties" to bring some specific configuration for...
Could be useful to configure the bridge with source and sink part running or not ? A bridge instance could be configure only for receiving by AMQP senders and sending...
Let's discuss if current implementation is good on using AMQP message annotation for specifying partition on sender side or it could be better to have this info inside the address....
Add a unit test with multiple sender connecting in parallel to the bridge and sending a bunch of messages each one (so a sort of multiple client periodic sending). Information...
Hi, I found a discrepancy in when a span is finished using the interceptor approach versus the wrapper one. As far as I understood, the duration time of a span...