[
https://issues.apache.org/jira/browse/NIFI-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310299#comment-15310299
]
ASF GitHub Bot commented on NIFI-1899:
--------------------------------------
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/483
I think the behavior you have now is perfect (it should auto decode from
base64) as it honors the user's intent.
As far as tracing to the parent you just need to connect the provenance
trail which can be done automatically through using the appropriate api
methods. @markap14 or @bbende could either of you help point in the right
direction here?
For splitting the processors up I *think* i like two different processors.
First is an ExtractEmailAttributes or some such name and then is a
ExtractEmailAttachments which inherits attributes from the parent flow file. I
haven't dug into this deep enough though to think my opinion is worth much
though :-)
Thanks!
> 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
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
