Restoring the way headers are displayed

[ErykCh]

Hi,

In version 2.4.1 the text is escaped:

Could you bring back the previous approach?

[weeco]

Starting with v2.4 we interpret all header values as strings rather than trying all the existing encoding types (AVRO, JSON etc.). I think we should bring it back again, but we are waiting for more feedback from other users.

[michaelandrepearce]

Maybe best to have a selectable strategy, some firms may decide on string only headers, others json, others may even use SchemaRegistry and encode them just like keys and values.

[fabio-deoliveira]

Hi! For the use case of the company I work for it would be great if we had the option to use the SchemaRegistry to encode and decode the values under headers. Any idea of when this feature could be integrated? Thank you in advance!

[harvidsen]

We end up putting a lot of timestamps in our headers, for traceability. If we use unix timestamps instead of strings we can reduce message size and improve downstream message parsing. Currently we don't do this because we would rather have human readable timestamps in the console. Therefore, it would be very nice to have decoded header values in the console, like we have with message value fields.