[
https://issues.apache.org/jira/browse/MINIFICPP-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ádám Markovics reassigned MINIFICPP-1457:
-----------------------------------------
Assignee: Ádám Markovics
> Implement InputRequirements
> ---------------------------
>
> Key: MINIFICPP-1457
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1457
> Project: Apache NiFi MiNiFi C++
> Issue Type: New Feature
> Reporter: Arpad Boda
> Assignee: Ádám Markovics
> Priority: Major
>
> InputRequirements already exist in NiFi.
> Processors can have the following "annotations":
> {code}
> enum Requirement {
> /**
> * This value is used to indicate that the Processor requires input
> from other Processors
> * in order to run. As a result, the Processor will not be valid if
> it does not have any
> * incoming connections.
> */
> INPUT_REQUIRED,
> /**
> * This value is used to indicate that the Processor will consume
> data from an incoming
> * connection but does not require an incoming connection in order to
> perform its task.
> * If the {@link InputRequirement} annotation is not present, this is
> the default value
> * that is used.
> */
> INPUT_ALLOWED,
> /**
> * This value is used to indicate that the Processor is a "Source
> Processor" and does
> * not accept incoming connections. Because the Processor does not
> pull FlowFiles from
> * an incoming connection, it can be very confusing for users who
> create incoming connections
> * to the Processor. As a result, this value can be used in order to
> clarify that incoming
> * connections will not be used. This prevents the user from even
> creating such a connection.
> */
> INPUT_FORBIDDEN;
> }
> {code}
> Should be used both in yaml config validation and population of C2 manifest
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
