[
https://issues.apache.org/jira/browse/NIFI-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574616#comment-14574616
]
Joseph Witt commented on NIFI-415:
----------------------------------
I believe doing what is proposed would require a change to the interface and be
of unclear value. A UUID is essential (and different) from the filename as
that is the unique identifier for that flowfile within nifi. But the filename
itself has no value within nifi. It only has value when interacting with an
outside system. If we do special handling for 'filename' what special handling
should we do for other attributes (where attributes are things stored in the
map) and a separate construct from uuid, entryDate, etc..
Can you provide the scenario behind this that prompted wanting to protect it?
> Framework should not allow an empty filename to be set
> ------------------------------------------------------
>
> Key: NIFI-415
> URL: https://issues.apache.org/jira/browse/NIFI-415
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Minor
> Labels: beginner
>
> StandardProcessSession and MockProcessSession should ignore the attribute if
> set via setAttributes and should throw an Exception if set via setAttribute,
> in the same manner as if attempting to set the "uuid" attribute of a flowfile.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
