You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Nicholas Carenza (JIRA)" <ji...@apache.org> on 2017/02/09 01:49:41 UTC

[jira] [Updated] (NIFI-3444) PutKinesisFirehose Optional message demarcator

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

Nicholas Carenza updated NIFI-3444:
-----------------------------------
    Summary: PutKinesisFirehose Optional message demarcator  (was: PutKenesisFirehose Optional message demarcator)

> PutKinesisFirehose Optional message demarcator
> ----------------------------------------------
>
>                 Key: NIFI-3444
>                 URL: https://issues.apache.org/jira/browse/NIFI-3444
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Nicholas Carenza
>            Priority: Trivial
>
> When using PutKenesisFirehose, flowfile content will be written as-is byte-for-byte to the firehose stream with no demarcation. For me at least, I expected there to be new lines in between but I can certainly understand this not being the default.
> I have seen many processors with options for message demarcating. Is that an option others might find useful on this processor and does it belong there?
> For now, I am using ReplaceText with '$' as the search and '<shift+enter>' as the replace.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)