[
https://issues.apache.org/jira/browse/NIFI-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381064#comment-15381064
]
Joseph Witt commented on NIFI-1899:
-----------------------------------
I think Dan's comment about these being separate JIRAs and ideally separate PRs
is a good one personally. Could do a parent ticket w/subtickets even. Makes
the review easier for one and we can bring bits in as they're ready.
Also, I think we should definitely create the parser/extract processors for
sure. Very valid cases to do so for dataflow management. However, I think the
architecture Dan suggests where NiFi is a bridge to help get data to Kafka for
Storm to then take over the deeper processing is perfectly fine.
[~ptgoetz] Does this sound about right to you? Anything of value you could see
being made available to Storm prior to data arrival or just get the bits of the
SMTP data onto Kafka. What about larger messages? Perhaps for larger messages
you could use the storm/nifi integration whereas for the majority of the
messages use Kafka. What are some good strategies to propose there?
> Create ListenSMTP & ExtractEmailAttachment processors
> -----------------------------------------------------
>
> Key: NIFI-1899
> URL: https://issues.apache.org/jira/browse/NIFI-1899
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Andre
> Fix For: 1.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
