nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (MINIFI-275) Configuration without IDs for components causes exceptions
Date Wed, 03 May 2017 04:05:04 GMT


ASF subversion and git services commented on MINIFI-275:

Commit d1e3694c32f566836d06577ab1da609b3f9dca14 in nifi-minifi-cpp's branch refs/heads/master
from [~kdoran]
[;h=d1e3694 ]

MINIFI-275 Bugfix for YAML Configs without Component IDs

This commit fixes a bug in which loading config YAML that did not
specify IDs (UUIDs) for components caused an exception. The logic
previously treated component IDs as required fields by loading them
without checking for existence. This commit updates the logic to
generate IDs when they are not specified in the YAML config. As part
of this fix, the logic for loading connections from YAML config was
modified to search by name or remote port id in the absence of source
id or remote id in the YAML config.

For fields that are required, useful error messages were added when
those fields are missing to assist users in self-diagnosing issues
related to invalid config files.

Some minor tweaks to the top level .gitignore are included with this

This closes #85.

Signed-off-by: Aldrin Piri <>

> Configuration without IDs for components causes exceptions
> ----------------------------------------------------------
>                 Key: MINIFI-275
>                 URL:
>             Project: Apache NiFi MiNiFi
>          Issue Type: Bug
>          Components: C++, Processing Configuration
>            Reporter: Aldrin Piri
>            Assignee: Kevin Doran
>            Priority: Blocker
>             Fix For: cpp-0.2.0
>         Attachments: config.TEST.yml
> One of the changes to how components are handled in C++ introduced a defect into the
original construct over the version 1 schema of the YAML.  
> The absence of this ID causes a YAML exception.  
> We should provide handling to support configurations how they were created originally,
possibly providing a default/generated ID where one isn't specified, and start laying the
foundation for versioned schemas as provided in our Java implementation.

This message was sent by Atlassian JIRA

View raw message