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.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
