[
https://issues.apache.org/jira/browse/NIFI-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende updated NIFI-1630:
------------------------------
Attachment: 0003-nifi-1630-PutUDP-processor-created.patch
[[email protected]] thanks for taking the time to refactor and use the
abstract class. You raised some great points about the timeout and charset
properties not applying to PutUDP, as well as the common code that could be
pushed up to the abstract class.
I'm adding a new patch that includes your commit followed by another one from
me that addresses those two ideas.
* I removed timeout and charset from the default properties, and added them to
PutSplunk so they are only added there.
* I also moved the acquire and release methods up to the abstract class and
updated PutSplunk to use those.
* One of the tests that tried to bind to 127.0.0.2 wouldn't work for me, so I
removed that.
* I also made one slight modification to the acquire method to not penalize the
FlowFile, mostly because we are already yielding and if the connection couldn't
be created it was more of an overall problem and not something specific to the
flowfile to warrant penalizing it
Let me know what you think of the latest patch, and thanks again for sticking
with this.
> 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.7.0
> Reporter: Matt Brown
> Priority: Minor
> Labels: beginner
> Attachments: 0001-nifi-1630-PutUDP-processor-created.patch,
> 0002-nifi-1630-PutUDP-processor-created.patch,
> 0003-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)
