You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2016/08/26 01:02:22 UTC

[jira] [Updated] (NIFI-2670) ConsumeKafka should support a configurable option for how to encode kafka key as attribute

     [ https://issues.apache.org/jira/browse/NIFI-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne updated NIFI-2670:
-----------------------------
    Status: Patch Available  (was: Open)

> 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)