[
https://issues.apache.org/jira/browse/NIFIREG-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604920#comment-16604920
]
Bryan Bende commented on NIFIREG-139:
-------------------------------------
[~jugi] I like this idea in theory, but I'm not sure we have the information to
correctly implement it...
When saving a flow to registry that references a CS from a parent group, the
versioned flow only has the id that was referenced.
For example, here is the properties section from PutHDFS when referencing a
keytab service from the parent group:
{code:java}
"properties" : {
"Compression codec" : "NONE",
"kerberos-credentials-service" : "8ac840fe-c730-392e-b1e2-a42dce0cde1d",
"Kerberos Relogin Period" : "4 hours",
"Conflict Resolution Strategy" : "fail"
}{code}
At the time of importing this versioned flow to a new instance, we don't know
what the name of the keytab service was in the previous instance that created
the flow, so I'm not sure how to line it up in the target environment.
The only thing I could think of would be to have a naming convention that could
be used to link components. So for example, maybe if the process group name is
"FOO## My Process Group" then we parse out whatever is before the ## which is
FOO in this case, and then look for controller services in parent groups where
the name also starts with "FOO##", and then if they match the type needed by
the processor then we can auto-assign it.
Keeping in mind that names are not unique so the best we could do is take the
first one found that matches the pattern.
> Nifi registry should pick up the controller service definitions while
> deploying a flow
> --------------------------------------------------------------------------------------
>
> Key: NIFIREG-139
> URL: https://issues.apache.org/jira/browse/NIFIREG-139
> Project: NiFi Registry
> Issue Type: Bug
> Affects Versions: 0.1.0
> Reporter: ohad israeli
> Priority: Critical
>
> I am trying to use the registry to copy a simple flow for example of
> httprequest->joltconversion->httpresponse.
> This flow is using the internal http context service which is installed and
> configured on the source (dev env). While deploying the flow to the target
> (prod env) the flow cant find the service on the target (prod end)
> to summarize, on deployment of a flow if the flow is using a service
> controller its setting should also be deployed on the target machine
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
