Vijay Mathew created NIFIREG-203:
------------------------------------

             Summary: Apache Nifi Registry with Git Integration
                 Key: NIFIREG-203
                 URL: https://issues.apache.org/jira/browse/NIFIREG-203
             Project: NiFi Registry
          Issue Type: Bug
            Reporter: Vijay Mathew


Please note that the below issue is occurring in the Windows environment.

>From the Nifi V1.7 UI, I am able to commit a test process group to the Git 
>Repository, however, when I try to import the process group from Git, UI 
>throws an exception "The Flow Registry with ID {} reports that no Flow exists 
>with Bucket {}, Flow {}, Version {}".Below is the logs from Registry

2018-09-26 19:45:11,543 WARN [NiFi Registry Web Server-19] 
o.a.n.registry.service.RegistryService The specified bucket id 
[64df4f73-160d-4c19-b47c-563804263300] does not exist.
2018-09-26 19:45:11,544 INFO [NiFi Registry Web Server-19] 
o.a.n.r.w.m.ResourceNotFoundExceptionMapper 
org.apache.nifi.registry.exception.ResourceNotFoundException: The specified 
bucket ID does not exist in this registry.. Returning Not Found response.
2018-09-26 19:45:49,325 ERROR [NiFi Registry Web Server-19] 
o.a.n.r.web.mapper.ThrowableMapper An unexpected error has occurred: 
java.lang.NullPointerException. Returning Internal Server Error response.
java.lang.NullPointerException: null
at org.eclipse.jgit.lib.Repository.resolve(Repository.java:526) 
~[org.eclipse.jgit-4.11.0.201803080745-r.jar:4.11.0.201803080745-r]
at org.eclipse.jgit.lib.Repository.resolve(Repository.java:487) 
~[org.eclipse.jgit-4.11.0.201803080745-r.jar:4.11.0.201803080745-r]
at 
org.apache.nifi.registry.provider.flow.git.GitFlowMetaData.getContent(GitFlowMetaData.java:422)
 ~[nifi-registry-framework-0.3.0.jar:0.3.0]
at 
org.apache.nifi.registry.provider.flow.git.GitFlowPersistenceProvider.getFlowContent(GitFlowPersistenceProvider.java:180)
 ~[nifi-registry-framework-0.3.0.jar:0.3.0]
at org.apache.nifi.registry.service.RegistryService.g



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to