You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joe Skora (JIRA)" <ji...@apache.org> on 2017/02/14 16:36:41 UTC
[jira] [Comment Edited] (NIFI-1985) ListenTCP should allow setting
incoming message delimiter
[ https://issues.apache.org/jira/browse/NIFI-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866078#comment-15866078 ]
Joe Skora edited comment on NIFI-1985 at 2/14/17 4:35 PM:
----------------------------------------------------------
[~bbende] I see what you mean, even though both ListenTCP and ListenUDP both inherit the {{Batching Message Delimiter}} property from the {{AbstractListenEventBatching Processor}}, it's only used on for output.
was (Author: jskora):
[~bbende] I see what you mean, thought both ListenTCP and ListenUDP both inherit the {{Batching Message Delimiter}} property from the {{AbstractListenEventBatching Processor}}, it's only used on for output.
> ListenTCP should allow setting incoming message delimiter
> ---------------------------------------------------------
>
> Key: NIFI-1985
> URL: https://issues.apache.org/jira/browse/NIFI-1985
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 0.6.0, 0.6.1
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
>
> Currently ListenTCP reads incoming messages separating them by "/n" and this is hard-coded. It would be useful to expose a property on the processor that allowed this to be changed by the user.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)