[jira] [Updated] (MINIFI-54) ConfigSchema duplicate validation only works when processors is not null

["Joseph Percivall (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MINIFI-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Percivall updated MINIFI-54:
-----------------------------------
    Fix Version/s: 0.1.0

> ConfigSchema duplicate validation only works when processors is not null
> ------------------------------------------------------------------------
>
>                 Key: MINIFI-54
>                 URL: https://issues.apache.org/jira/browse/MINIFI-54
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>            Reporter: Bryan Rosander
>             Fix For: 0.1.0
>
>
> ConfigSchema has logic to detect duplicate processor, connection, and remote processing group names.  This is to help MiNiFi ensure it can generate a valid flow.
> Unfortunately, the check is short circuited if processors are null, regardless of which duplicates it is checking for, causing for possibly missing validation errors.
> https://github.com/apache/nifi-minifi/blob/2d1e43e73b90df55abc71845160b6422d7a6f03f/minifi-commons/minifi-commons-schema/src/main/java/org/apache/nifi/minifi/commons/schema/ConfigSchema.java#L122
> Should be changed to a null check on the names parameter



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)