[
https://issues.apache.org/jira/browse/NIFI-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438321#comment-15438321
]
ASF subversion and git services commented on NIFI-2670:
-------------------------------------------------------
Commit 58e0ce7f92f708422276a68f4e04c61470c71b11 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=58e0ce7 ]
NIFI-2670: This closes #954. Expose option for how to interpret Kafka Key -
hexadeimal encoding or UTF-8 String
> ConsumeKafka should support a configurable option for how to encode kafka key
> as attribute
> ------------------------------------------------------------------------------------------
>
> Key: NIFI-2670
> URL: https://issues.apache.org/jira/browse/NIFI-2670
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 1.0.0
>
>
> Previously, ConsumeKafka / GetKafka added the kafka key as an attribute to
> the flowfile, assuming that the key was in UTF-8 format. Recently, this was
> changed to use a hex encoding. This could break flows, as it is not backward
> compatible. We should instead make this a configurable option with the
> default being UTF-8 Encoded.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
