[
https://issues.apache.org/jira/browse/NIFI-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204228#comment-15204228
]
Bryan Bende commented on NIFI-1630:
-----------------------------------
Joe/Matt,
Sure... We recently added a PutSplunk processor which is essentially PutTCP +
PutUDP behind the scenes, and as part of this we created
AbstractPutEventProcessor in nifi-processor-utilities:
https://github.com/apache/nifi/blob/master/nifi-commons/nifi-processor-utilities/src/main/java/org/apache/nifi/processor/util/put/AbstractPutEventProcessor.java
We may want to consider having PutUDP extend AbstractPutEventProcessor so that
everything leverages the same underlying networking code (also in
nifi-processor-utilities). For reference, PutSplunk is here:
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-splunk-bundle/nifi-splunk-processors/src/main/java/org/apache/nifi/processors/splunk/PutSplunk.java
I think the main difference between AbstractPutEventProcessor and Matt's
PutUDP, is that AbstractPutEventProcessor supports two modes - one is sending a
FlowFile as a datagram, and the other is breaking up an incoming FlowFIle into
many datagrams based on a delimiter (think a large file of separated by new
lines, and sending each line as a datagram).
> Create PutUDP Processor
> -----------------------
>
> Key: NIFI-1630
> URL: https://issues.apache.org/jira/browse/NIFI-1630
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 0.6.0
> Reporter: Matt Brown
> Priority: Minor
> Labels: beginner
> Attachments: 0001-nifi-1630-PutUDP-processor-created.patch
>
>
> Create a processor to send each FlowFile as a datagram to a UDP server.
> Processor must provide properties to allow the user to configure the
> destination host address and port to send to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
