[
https://issues.apache.org/jira/browse/NIFI-16026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-16026.
-----------------------------------
Fix Version/s: 2.11.0
Resolution: Fixed
> Write message headers as hexadecimal strings in ConsumeKafka
> ------------------------------------------------------------
>
> Key: NIFI-16026
> URL: https://issues.apache.org/jira/browse/NIFI-16026
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Alaksiej Ščarbaty
> Assignee: Alaksiej Ščarbaty
> Priority: Major
> Fix For: 2.11.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> h2. Problem
> {{{}ConsumeKafka{}}}'s *Header Encoding* property is charset-only
> ({{{}Charset.forName(...){}}}, {{{}ConsumeKafka.java:197{}}}/{{{}:379{}}}).
> Binary headers (e.g. little-endian Int64) are corrupted by UTF-8 decoding and
> unrecoverable. The *Key Attribute Encoding* property already supports {{HEX}}
> ({{{}KeyEncoding{}}} enum), but headers have no binary-safe path.
> h2. Ask
> Make header format configurable to support either strings (according to the
> provided charset in {*}Header Encoding{*}) or hex format for Kafka message
> headers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
