[
https://issues.apache.org/jira/browse/NIFI-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15865872#comment-15865872
]
Bryan Bende commented on NIFI-1985:
-----------------------------------
[~jskora] this is still a valid issue, it doesn't apply to ListenUDP because
UDP is connection-less.
Currently there is a hard-coded \n delimiter in the socket handlers used by
ListenTCP, we should at least have a property on the processor for "Incoming
Message Delimiter" and pass that value down. If we want to support more options
we could have a strategy for how we demarcate incoming messages, maybe one is
based on a delimiter like above, maybe another is based on number of bytes read.
> 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)
