Page History

• Adds the ability for producers to set standard header key=value value pairs
• No incompatible client api change (only new methods)
• Allows users to specify the serialization of the header value per header
• Compact key space
• Provides a standardized interface to eco systems of tools that then can grow around the feature

The disadvantage of this proposal is:

• Change to the message object

Add a headers field Map<int, byte[]> to both ProducerRecord and ConsumerRecord

• Accessor methods of void setHeader(int, byte[]) and byte[] getHeader(int) added to interface of the ProducerRecord.
• Accessor methods of byte[] getHeader(int) added to interface of the ConsumerRecord. (immutable as such no set required)