You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Gábor Gyimesi (Jira)" <ji...@apache.org> on 2023/03/31 10:12:00 UTC

[jira] [Updated] (MINIFICPP-612) Improve schedule/ontrigger structure of Processors

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

Gábor Gyimesi updated MINIFICPP-612:
------------------------------------
    Fix Version/s:     (was: 0.14.0)

> Improve schedule/ontrigger structure of Processors
> --------------------------------------------------
>
>                 Key: MINIFICPP-612
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-612
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Improvement
>            Reporter: Marc Parisi
>            Priority: Major
>
> Processors follow Java convention in their design. This has led to following the same control flow that exists within NiFi; however, we can take some liberties of using template metaprogramming to improve the user experience. 
> This ticket will be responsible for covering onTrigger and onSchedule. The underlying architectural decisions will remain the same, but with a focus on allowing design time decisions to be caught and fixed at compile time versus run time. The first area to tackle is input requirements within Processors. Currently if we specified a limitation it wouldn't be enforced gracefully or at all until runtime. This should not be the case. Developers who forbid input within a processor should never have the ability to call session->get() and this should result in a compile time error. With template metapogramming and SFINAE, we should be able to make this a compile time restriction and better impose enforcement within the design



--
This message was sent by Atlassian Jira
(v8.20.10#820010)