1. Import a template T1 with a processor referring controller service C1 of type A (Say DBCPConnectionPool)
2. Import a second template T2 with another processor referring to controller service C2 of type A.
T1 processor is configured to use C1
T2 processor is configured to use C2
T1 and T2 processors are both configured to use C1
It appears you are trying to import templates with new services that dont exist yet in NiFi
Upon import of a template Kylo will first look to see if the defined controller service (CS) exists in NiFi by matching by id, then name, then type
If there is a match it will use the existing service, otherwise it will create one of the correct type and use that.
After importing the template one can explicitly set the CS property value to the correct one and it will be set correctly for the feeds in that NiFi instance.
For your instance you need to create the new CS in NiFi (if it doesnt exist) and set it in Kylo's registration step
In my case, Data Ingest import template had created MySQL controller service (type DBCP connection pool).
Then, I imported Teradata Data Ingest template, which has Teradata-DBC controller service (type DBCP connection pool).
The feed created from Teradata Data Ingest template got MySQL controller service assigned in processor. It should have been assigned Teradata-DBC.