Hi All, and Antony (author of below article) i came across this article which seemed interesting: Introducing Confluent’s Parallel Consumer Message Processing Client <https://www.confluent.io/blog/introducing-confluent-parallel-message-processing-client/>
I would like to use the key-level ordering strategy mentioned in the article to scale my consumers, however I would like to check how the offset commits are handled in this strategy e.g. on partition 1, key1 has offsets 20 and 30 respectively and on the same partition key2 has offset 40. With key-level ordering model, key2 will be processed by a different thread in background and might gets processed before events related to key1, in this case offset for key2 will be committed before key1 gets processed ? How is this handled?
