It looks like it's not possible to specify Consumer arguments when using any of the Receiver's consume* methods. I'm not sure if there was any use for them in the past, but with RabbitMQ 3.9 streams, if consuming them with AMQP client, the x-stream-offset argument is used to specify the offset at which consumption will start.
Since we already have the ability to pass ConsumeOptions to Receiver.consume* methods, I suggest we add an empty-by-default (or null) map of args to that class, so that later we can pass it to channel.basicConsume.
It looks like it's not possible to specify Consumer arguments when using any of the Receiver's
consume*
methods. I'm not sure if there was any use for them in the past, but with RabbitMQ 3.9 streams, if consuming them with AMQP client, thex-stream-offset
argument is used to specify the offset at which consumption will start.Since we already have the ability to pass
ConsumeOptions
toReceiver.consume*
methods, I suggest we add an empty-by-default (or null) map of args to that class, so that later we can pass it tochannel.basicConsume
.