[
https://issues.apache.org/jira/browse/NIFI-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311415#comment-15311415
]
ASF GitHub Bot commented on NIFI-1899:
--------------------------------------
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/483
@bbende
You are correct, the provenance trail is there, however, generally it seems
like the Split* processors tend to add the split source information as well in
the shape of
> `segment.original.filename The filename of the parent FlowFile`
The behaviour is also documented
[here](https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html#split-content-one-to-many):

For example, assuming I use the processors to perform data archival, having
the parent.uuid as an attribute would allow me to draw a direct and accessible
relationship between the two flowfiles.
Maybe I am overcomplicating but I simply couldn't find a documented way of
accessing the provenance parent UUID from the Expression Language.
> 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)