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

ASF GitHub Bot commented on NIFI-3173:
--------------------------------------

Github user JPercivall commented on the issue:

    https://github.com/apache/nifi/pull/1318
  
    @markap14 I hit a case where a CS wasn't preserved. I'll outline it in the 
same way you listed your example in the comments:
    
    G1 -- C1
    |
    |
    G2 -- C2
    |    \
    |      P1
    G3   
    | \   \
    |    \   P2
    G4  G5
    |        |
    |        |
    P3    P4
    
    P3 and P4 are HandleHttpRequest and HandleHttpResponse which reference C1 
(HttpContextMap) and P2 is ReplaceText. They form an Http Service which takes 
any request and returns "test".
    
    P1 is an InvokeHttp which references an SSLController Service C2 which is 
in the same group.
    
    When making the template (by being in G1, selecting G2 and clicking create 
template), the Http Service explained first is created as expected but C2 is 
not added to the template at all.
     


> When creating a template Controller Services can end up being not properly 
> scoped
> ---------------------------------------------------------------------------------
>
>                 Key: NIFI-3173
>                 URL: https://issues.apache.org/jira/browse/NIFI-3173
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Joseph Percivall
>            Assignee: Mark Payne
>             Fix For: 1.1.1
>
>
> Steps to reproduce:
> 1: From the root group create a Controller Service (ie. HttpContextMap)
> 2: Create two child process groups
> 3: In each child group create a processor that references the CS (ie. 
> HandleHttpRequest and HandleHttpResponse)
> 4: Create a template of the two child PGs
> 5: Export the template
> 6: Import template into a clean instance
> 7: See the Controller service not scoped to the root level but instead scoped 
> to one of the child PGs
> I believe the template creation is grabbing the first instance of the CS when 
> it sees it and ignores the other references, instead of taking it at the 
> highest level. I also believe this is related to NIFI-3129
> https://issues.apache.org/jira/browse/NIFI-3129



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

Reply via email to