This is a quick hack which we can use, but I'd rather have a more robust fix. Also, this approach is problematic if users have custom headers which are prefixed with kafka_.
Would you consider emitting Kafka headers from the input as an array using structured metadata and maybe call the field kafka_header? This would be a breaking change for existing components, but maybe we can just do it for as part of FranzRecordToMessageV1() in internal/impl/kafka/franz_reader.go in #2918.
This seems better as a quick fix - but yea it would be better to have some way to be more robust about this for the migrator as you mention in the PR description. Maybe can happen after Ash's Kafka refactor PR
This is a quick hack which we can use, but I'd rather have a more robust fix. Also, this approach is problematic if users have custom headers which are prefixed with
kafka_
.Would you consider emitting Kafka headers from the input as an array using structured metadata and maybe call the field
kafka_header
? This would be a breaking change for existing components, but maybe we can just do it for as part ofFranzRecordToMessageV1()
ininternal/impl/kafka/franz_reader.go
in #2918.