[jira] [Commented] (NIFI-7460) Nifi throws NullPointerException if some fields in Versioned Flow are null

["Sri Harsha Chavali (Jira)" <ji...@apache.org>]

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

Sri Harsha Chavali commented on NIFI-7460:
------------------------------------------

I took the code for this fix from master and incorporated into 1.11.4 and built my own nar file and noticed a one more thing which I wanted to share:
 # Disabled process groups become out of sync with registry. Disabled process groups are marked * - Local changes have been made. I don't know if this is expected. 

we are on nifi-registry-0.6.0 and in our current nifi-1.9.2 environment and the disabled PGs don't show any local changes. After incorporating this fix into 1.11.4 code and building the nar file, I see that there are local changes in the new deployment. 

> Nifi throws NullPointerException if some fields in Versioned Flow are null
> --------------------------------------------------------------------------
>
>                 Key: NIFI-7460
>                 URL: https://issues.apache.org/jira/browse/NIFI-7460
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.12.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> I have a flow in the registry where the 'autoTerminatedRelationships' for a processor are null. This causes NiFi to throw a NPE, which prevents me from getting to the UI. NiFi should avoid throwing the NPE, should provide better logging to indicate where the problem is (which Process Group), and should in most cases just log errors and transition a PG's Versioned Flow State to a state of SYNC_FAILURE with an appropriate error instead of throwing Exceptions that could prevent the UI from responding



--
This message was sent by Atlassian Jira
(v8.3.4#803005)