[
https://issues.apache.org/jira/browse/NIFI-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438230#comment-15438230
]
ASF GitHub Bot commented on NIFI-2670:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/954
NIFI-2670: Expose option for how to interpret Kafka Key - hexadeimal
encoding or UTF-8 String
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-2670
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/954.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #954
----
commit 50842cb24e185e931b81880c3c33afcc22819736
Author: Mark Payne <[email protected]>
Date: 2016-08-26T01:00:45Z
NIFI-2670: 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)
