You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2018/01/10 19:44:00 UTC

[jira] [Updated] (MINIFICPP-363) Allow for unqualified class names in YAML configuration

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

Aldrin Piri updated MINIFICPP-363:
----------------------------------
    Fix Version/s: 0.4.0

> Allow for unqualified class names in YAML configuration
> -------------------------------------------------------
>
>                 Key: MINIFICPP-363
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-363
>             Project: NiFi MiNiFi C++
>          Issue Type: Improvement
>            Reporter: Andrew Christianson
>            Assignee: Andrew Christianson
>            Priority: Minor
>             Fix For: 0.4.0
>
>
> Current configurations require processor class names that look like this:
> {code}
> org.apache.nifi.processors.standard.GenerateFlowFile
> {code}
> This is extremely verbose and essentially only is there to support configs converted from Java. The class names currently have no meaning in the cpp codebase.
> Allowing unqualified classes will help simplify hand-configured YAML configurations and make things easier to read. New configurations would support classes specified as such:
> {code}
> GenerateFlowFile
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)