[🧹 CHORE]: Possible typo in AMQP-driver property named multiple_ack

[Kaspiman]

No duplicates 🥲.

• I have searched for a similar issue.

What should be improved or cleaned up?

Let's find the multiple_ack param - there are no results.

Let's find the "multiple_ask" roadrunner-server/amqp - i found mapping multiple_ask => MultipleAck.

But in AMQP config we have only multiple_ack param.

---

Additional: check the tests: https://github.com/roadrunner-server/rr-e2e-tests/blob/master/plugins/jobs/amqp/jobs_amqp_test.go

[rustatian]

Hey @embargo2710 👋🏻
Yeah, this is def typo. Will fix that, thanks 👍🏻

[Kaspiman]

@rustatian
Since we met in this issue, can you add a more understandable description for the "multiple_ack" parameter?

multiple_ack - this delivery, along with all prior unacknowledged deliveries on the same channel, will be acknowledged. This feature is beneficial for batch processing of deliveries and is applicable only for Ack, not for Nack.

what is the "this delivery" and what could heapen when multiple_ack is true? At what moment of Jobs/task lifecycle can this happen?

[rustatian]

Delivery is the messages that are delivered through the queue. This is the default rabbitmq term. Communication with the rabbitmq broker is done through the channels. So, for example, if you have the 10 messages that are being processed by the workers, and you use multiple_ack=true, then when the first message (JOB) is processed, it'll auto-acknowledge all the previous messages (Deliveries): https://www.rabbitmq.com/confirms.html#consumer-acks-multiple-parameter