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

[jira] [Updated] (MINIFICPP-219) Build test harness for Processors

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

marco polo updated MINIFICPP-219:
---------------------------------
    Fix Version/s: 0.3.0

> Build test harness for Processors
> ---------------------------------
>
>                 Key: MINIFICPP-219
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-219
>             Project: NiFi MiNiFi C++
>          Issue Type: Bug
>            Reporter: marco polo
>            Assignee: marco polo
>             Fix For: 0.3.0
>
>
> Build a test harness for Processors. A straw man exists in [1]. In this example, one creates a TestPlan object, and defines the processors. The repositories, connections, contexts, and sessions are created for the developer. An example in the commit, below, is as follows
> {code:java}
> std::shared_ptr<core::Processor> getfile = plan->addProcessor("GetFile", "getfileCreate2");
> std::shared_ptr<core::Processor> logattribute = plan->addProcessor("LogAttribute", "logattribute", core::Relationship("success", "description"), true);
> {code}
> In the example above, two processors are created. The first of which is connected to the second processor with the success relationship. We should extend this idea to functionally cover all that is needed. The straw man provides the ability to auto create connections for processors, run the trigger function and/or run a verifier function instead of the onTrigger function for a processor. 
> [1] https://github.com/apache/nifi-minifi-cpp/pull/110/commits/39c78597a44c0bcbb4e3b41edc073a012842d1db



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