[
https://issues.apache.org/jira/browse/NIFI-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869249#comment-15869249
]
Andre commented on NIFI-940:
----------------------------
The comment that I would make from a "user" standpoint is that having to use an
updateattribute processor will cause a significant overhead to simple tasks
like saving based on date, sending host, etc.
I remember reading comments in the past that to maximise performance DFMs
should strive to use as few processors as possible and this seems like a good
example of that. Should I have to create a provenance event just to set a
filename? Perhap yes (from a provenance point if view) but if it is the case
then we may want to document this rationale
> Expose 'filename' as a Property on PutFile, PutHDFS, PutFTP, PutSFTP, and
> other Put-esque processors
> ----------------------------------------------------------------------------------------------------
>
> Key: NIFI-940
> URL: https://issues.apache.org/jira/browse/NIFI-940
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 0.3.0
> Reporter: Michael Kobit
> Assignee: Andre
>
> Allow a NFM to set the filename to save files as. Should support Expression
> language, and default to '${filename}'
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
