Additional transaction info - number of commands in transaction shown in begin message #284
Description
Is your feature request related to a problem? Please describe.
As OLR is already doing the hard work of transactions sorting and prevents interleaving as explained in transaction-processing it will be beneficial for recipient to know the transaction length before reading all transaction messages - e.g. memory allocation, special handling of big transactions etc...
Describe the solution you'd like
Having additional field "length" in transaction begin message by default or enabled via format.attributes (0x0008 — add transaction length field to transaction begin message).
Describe alternatives you've considered
- Using single message per transaction approach, but this hits Kafka limits
Additional context