You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Marton Szasz (Jira)" <ji...@apache.org> on 2020/11/30 13:05:00 UTC
[jira] [Updated] (MINIFICPP-1415) Use raw pointer overloads of
onTrigger and onSchedule when possible
[ https://issues.apache.org/jira/browse/MINIFICPP-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marton Szasz updated MINIFICPP-1415:
------------------------------------
Description:
To avoid mandatory shared ownership of ProcessSessionFactory, ProcessSession and ProcessContext, possibly enabling future refactoring to simplify processor code by removing these overloads.
This would also simplify processor implementation which is important for third-party extensibility. I would love to eventually see an ecosystem where people start creating their own independent processors for minifi c++ to interface with other software.
original idea: https://github.com/apache/nifi-minifi-cpp/pull/943#discussion_r532575479
was:
To avoid mandatory shared ownership of ProcessSessionFactory, ProcessSession and ProcessContext, possibly enabling future refactoring to simplify processor code by removing these overloads.
This would also simplify processor implementation which is important for third-party extensibility. I would love to eventually see an ecosystem where people start creating their own independent processors for minifi c++ to interface with other software.
> Use raw pointer overloads of onTrigger and onSchedule when possible
> -------------------------------------------------------------------
>
> Key: MINIFICPP-1415
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1415
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Marton Szasz
> Priority: Minor
>
> To avoid mandatory shared ownership of ProcessSessionFactory, ProcessSession and ProcessContext, possibly enabling future refactoring to simplify processor code by removing these overloads.
> This would also simplify processor implementation which is important for third-party extensibility. I would love to eventually see an ecosystem where people start creating their own independent processors for minifi c++ to interface with other software.
>
> original idea: https://github.com/apache/nifi-minifi-cpp/pull/943#discussion_r532575479
--
This message was sent by Atlassian Jira
(v8.3.4#803005)