[
https://issues.apache.org/jira/browse/NIFI-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374161#comment-15374161
]
Matt Burgess commented on NIFI-1152:
------------------------------------
Including the default relationships for InvokeScriptedProcessor was an
oversight on my part (i.e. cut-and-paste error from ExecuteScript). No default
relationships should be supplied by InvokeScriptedProcessor if none are given
by the scripted processor (or if there is an error in the script itself).
Otherwise the scripted processor would be using provided relationships, which
is inconsistent with all other processors ("real" processors must provide their
own). The idea behind InvokeScriptedProcessor is that the script defines a
"full" Processor implementation that acts as if it were a "real" one.
I think the relationships should be removed and the doc updated to reflect
that. Just my two cents :)
> StandardProcessSession and MockProcessSession should handle transfer to
> unregistered relationship correctly
> -----------------------------------------------------------------------------------------------------------
>
> Key: NIFI-1152
> URL: https://issues.apache.org/jira/browse/NIFI-1152
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Affects Versions: 1.0.0, 0.6.0, 0.7.0, 0.6.1
> Reporter: Mark Payne
> Assignee: Joseph Witt
> Labels: beginner, newbie
> Fix For: 1.0.0
>
> Attachments:
> 0001-Fix-for-NIFI-1838-NIFI-1152-Code-modification-for-ty.patch
>
>
> If a processor calls ProcessSession.transfer(flowFile,
> NON_EXISTENT_RELATIONSHIP) the NiFi framework will throw a
> FlowFileHandlingException. However, the Mock Framework simply allows it and
> does not throw any sort of Exception. This needs to be addressed so that the
> Mock framework functions the same way as the normal NiFi framework.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
