Brian Ghigiarelli created NIFI-854:
--------------------------------------
Summary: Controller Service Not Created from Processor inside Group
Key: NIFI-854
URL: https://issues.apache.org/jira/browse/NIFI-854
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 0.3.0
Reporter: Brian Ghigiarelli
Controller Services are created when a Processor on the root canvas is created
from a Template instantiation on the canvas; however, this does not work for
templates that have Processors within Process Groups.
Steps to reproduce:
1. Start fresh (clean canvas, no controller services)
2. Create Process Group and go into it
3. Add DetectDuplicate processor to Process Group
4. Configure DetectDuplicate processor with a new
DistributedMapCacheClientService and enable that service so that the
DetectDuplicate processor is valid and ready to run
5. Navigate to root canvas (see the Process Group)
6. Create template from root canvas (name: "Controller Service Test")
7. Delete everything from the canvas and disable + delete the controller
service so that we're essentially back to the start
8. Drag and drop the "Controller Service Test" template onto the canvas
(expecting that everything will be auto-created)
9. Navigate into the Process Group and notice that the DetectDuplicate
processor is invalid because the DistributedMapCacheClientService ID cannot be
found
As an additional test, I created a template with a processor at the top-level
and one inside the Process Group that are using the same Controller Service,
and that works just fine. My guess is that the top-level processor is used to
create the Controller Service and the inner-processor picks it up by that same
ID.
Expected behavior: Controller Services referenced by Processors within Process
Groups are created on template instantiation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
