[jira] [Comment Edited] (NIFI-2522) Controller Service scoping appears to make faulty assumption about parent identifier

["Mark Payne (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414173#comment-15414173 ] 

Mark Payne edited comment on NIFI-2522 at 8/9/16 8:21 PM:
----------------------------------------------------------

[~joewitt] as far as I can tell, this is working properly. I was able to create a Controller Service as described in NIFI-2299, and it worked just as I expected.


was (Author: markap14):
[~joewitt] as far as I can tell, this is working properly. I was able to create a Controller Service as described in NIFI-2299, and it worked just as I expected it.

> Controller Service scoping appears to make faulty assumption about parent identifier
> ------------------------------------------------------------------------------------
>
>                 Key: NIFI-2522
>                 URL: https://issues.apache.org/jira/browse/NIFI-2522
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Joseph Witt
>            Assignee: Mark Payne
>            Priority: Critical
>             Fix For: 1.0.0
>
>
> In testing the InvokeScriptedProcessor support for calling controller services I found that the controller service scope was tied to the processor the script was contained in rather than the process group.  Perhaps it is pulling the wrong parent ID rather than ensuring it gets the parent process group's id.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)