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

Bryan Bende commented on NIFI-6577:
-----------------------------------

David's description sounds correct. When version controlling a process group, 
it will capture all self-contained components (processors and controller 
services). If a component with in the group references a component outside the 
group, then those are expected to be linked back together in the next 
environment, such as deploying from dev to prod where each environment has a 
shared service at the root group.

In your case since you are using nifi-stateless, I would expect that you want 
everything to be contained in a single process group which can be a deployable 
unit, so you would create service inside the versioned process group.

> Controller Services are not getting committed while committing job-flow 
> (associated with existing job) into NiFi Registry
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-6577
>                 URL: https://issues.apache.org/jira/browse/NIFI-6577
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: sanjiv kumar
>            Priority: Major
>              Labels: nifi-registry
>
>  have written simple job which do the file listing from S3 , related to that 
> , I have attached controller services (AWS Credentials Provider service) 
> which generally contains AWS credentials stuff . I thought while committing 
> Job into NiFi-Registry those services should also be a part of that , but It 
> seems that is not the case . I am getting exception below
>  
> {{kubectl logs nififn-sample-job-pfrn4 -n nifi-fn-operator-system
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/usr/share/nifi-1.8.0/lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/usr/share/nififn/lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/usr/share/nififn/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type 
> [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> Exception in thread "main" java.lang.IllegalArgumentException: context is not 
> valid: 'AWS Credentials Provider service' validated against 
> 'b7f1e9d1-9ba8-321c-8c7c-31dab0ef0161' is invalid because Property references 
> a Controller Service that does not exist
> 'AWS Credentials Provider service' validated against 
> 'b7f1e9d1-9ba8-321c-8c7c-31dab0ef0161' is invalid because Invalid Controller 
> Service: b7f1e9d1-9ba8-321c-8c7c-31dab0ef0161 is not a valid Controller 
> Service Identifier
>       at 
> org.apache.nifi.fn.core.FnProcessorWrapper.initialize(FnProcessorWrapper.java:125)
>       at 
> org.apache.nifi.fn.core.FnProcessorWrapper.runRecursive(FnProcessorWrapper.java:136)
>       at org.apache.nifi.fn.core.FnFlow.runOnce(FnFlow.java:201)
>       at org.apache.nifi.fn.runtimes.Program.main(Program.java:104)}}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to