nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From joewitt <>
Subject [GitHub] nifi pull request: NIFI-1899 - Introduce ExtractEmailAttachments processor
Date Wed, 01 Jun 2016 13:25:40 GMT
Github user joewitt commented on the pull request:
    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 :-)

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message