[
https://issues.apache.org/jira/browse/MINIFICPP-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817872#comment-16817872
]
Mr TheSegfault commented on MINIFICPP-694:
------------------------------------------
For some processors this may not make sense – but as we transition to minifi
using nanofi, python processors, and other similar bound languages will serve
well from this effort. Communication will likely have to be within the
structures for that class.
This ticket will also become important within the confines of scheduling. If
someone wants their C or python processor to be run within minifi as part of a
deployed flow, they will then need to implement these callbacks, but that is
not always the case.
> Ensure that processor consist of proper phases
> ----------------------------------------------
>
> Key: MINIFICPP-694
> URL: https://issues.apache.org/jira/browse/MINIFICPP-694
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Mr TheSegfault
> Assignee: Arpad Boda
> Priority: Major
> Labels: nanofi
> Fix For: 0.7.0
>
>
> Ensure that processor consist of proper phases – such as "onSchedule" – that
> is when it is scheduled and onTrigger, when it is invoked. Ensure consistent
> naming and that custom processors provide this capability.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
