Hi, I understand in most of cases, we should keep log immutable. However, when it goes to event sourcing (Ben Stopford <https://www.confluent.io/blog/author/ben/> and Neha Narkhede <https://www.confluent.io/blog/author/neha-narkhede/> have a series of posts: Messaging as the Single Source of Truth <https://www.confluent.io/blog/messaging-single-source-truth/>, Using Apache Kafka as a Scalable, Event-Driven Backbone for Service Architectures <https://www.confluent.io/blog/apache-kafka-for-service-architectures/> and Event sourcing, CQRS, stream processing and Apache Kafka: What’s the connection <https://www.confluent.io/blog/event-sourcing-cqrs-stream-processing-apache-kafka-whats-connection/>), we need to evolve the messages -- upgrade the message from lower version to newer version. Regarding evolve of the message, Michiel Overeem, etc have documented the patterns in the paper: http://files.movereem.nl/2017saner-eventsourcing.pdf
So, there's a strong requirement when kafka is serving as event sourcing. Is there any plan that kafka will support mutation of logs? If it's too dangerous to update message online, at least provide a way to upgrade the messages in batch. -- Regards, iVen
