[
https://issues.apache.org/jira/browse/NIFI-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559734#comment-14559734
]
Mark Payne commented on NIFI-606:
---------------------------------
Hmm now that you bring this up, I wish I'd done this differently to begin with;
wish I'd made DataPacket Generic and had DataPacket<InputStream> and
DataPacket<byte[]> so that we didn't need the two.
I don't like pushing the NiFiDataPacket class back into
nifi-site-to-site-client just because we'd have DataPacket and NiFiDataPacket
there together and it would be very confusing. If we wanted to merge the two I
think we should take the route of a Generic.. But given that this is only the
second use case we've come across and there may well be more, I think that we
should just create a new one in the nifi-storm-spout project; this way, if
Storm needs something different than Spark needs we have that freedom without
muddying the waters.
Sorry, just thinking out loud. Short answer: I like Option #1 personally :)
> Add a NiFi Storm Spout
> ----------------------
>
> Key: NIFI-606
> URL: https://issues.apache.org/jira/browse/NIFI-606
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
>
> A nice integration would be a Storm spout that could pull data from NiFi,
> much like the Spark receiver does.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
