[
https://issues.apache.org/jira/browse/MINIFICPP-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Hunyadi updated MINIFICPP-1206:
------------------------------------
Description:
*Acceptance criteria:*
# GIVEN a python script that transfers to *REL_FAILURE* and an
ExecutePythonProcessor set up with a *"Script File"* attribute, but not with
*"Script Body"*
WHEN the processor is triggered
THEN any consumer using the *failure* relationship as source should receive
the transfered data
# GIVEN an ExecutePythonProcessor set up with a *"Script Body"* attribute that
transfers to *REL_SUCCESS*, but not *"Script File"*
WHEN the processor is triggered
THEN any consumer using the *success* relationship as source should receive
the transfered data
# GIVEN an ExecutePythonProcessor set up with a *"Script Body"* attribute that
transfers to *REL_FAILURE*, but not *"Script File"*
WHEN the processor is triggered
THEN any consumer using the *failure* relationship as source should receive
the transfered data
# GIVEN an ExecutePythonProcessorset up with both *"Script Body"* and *"Script
File"*
WHEN the processor is triggered
THEN an error should be logged and neither the inline script nor the script
body should be executed
*Background:*
We would like to start supporting inline python scripts in
ExecutePythonProcessor. Someone already tried to add support for this option,
but he did not finish the implementation.
*Proposal:*
The related dead code was removed in
[PR-768|https://github.com/apache/nifi-minifi-cpp/pull/768]. The implementation
can be started by reverting this commit. Upon implementation, please check if
failures are handled properly and add tests for this branch as well.
was:
*Acceptance criteria:*
# GIVEN a python script that transfers to *REL_FAILURE* and an
ExecutePythonProcessor set up with a *"Script File"* attribute, but not "Script
Body"
WHEN the processor is triggered
THEN any consumer using the *failure* relationship as source should receive
the transfered data
# GIVEN an ExecutePythonProcessor that is set up with a *"Script Body"*
attribute that transfers to *REL_SUCCESS*, but not *"Script File"*
WHEN the processor is triggered
THEN any consumer using the *success* relationship as source should receive
the transfered data
# GIVEN an ExecutePythonProcessor that is set up with a *"Script Body"*
attribute that transfers to *REL_FAILURE*, but not *"Script File"*
WHEN the processor is triggered
THEN any consumer using the *failure* relationship as source should receive
the transfered data
# GIVEN an ExecutePythonProcessor that is set up with both *"Script Body"* and
*"Script File"*
WHEN the processor is triggered
THEN an error should be logged and neither the inline script nor the script
body should be executed
*Background:*
We would like to start supporting inline python scripts in
ExecutePythonProcessor. Someone already tried to add support for this option,
but he did not finish the implementation.
*Proposal:*
The related dead code was removed in
[PR-768|https://github.com/apache/nifi-minifi-cpp/pull/768]. The implementation
can be started by reverting this commit. Upon implementation, please check if
failures are handled properly and add tests for this branch as well.
> Implement inline-script support for ExecutePythonProcessor
> ----------------------------------------------------------
>
> Key: MINIFICPP-1206
> URL: https://issues.apache.org/jira/browse/MINIFICPP-1206
> Project: Apache NiFi MiNiFi C++
> Issue Type: Improvement
> Affects Versions: 0.7.0
> Reporter: Adam Hunyadi
> Assignee: Adam Hunyadi
> Priority: Minor
> Fix For: 1.0.0
>
>
> *Acceptance criteria:*
> # GIVEN a python script that transfers to *REL_FAILURE* and an
> ExecutePythonProcessor set up with a *"Script File"* attribute, but not with
> *"Script Body"*
> WHEN the processor is triggered
> THEN any consumer using the *failure* relationship as source should receive
> the transfered data
> # GIVEN an ExecutePythonProcessor set up with a *"Script Body"* attribute
> that transfers to *REL_SUCCESS*, but not *"Script File"*
> WHEN the processor is triggered
> THEN any consumer using the *success* relationship as source should receive
> the transfered data
> # GIVEN an ExecutePythonProcessor set up with a *"Script Body"* attribute
> that transfers to *REL_FAILURE*, but not *"Script File"*
> WHEN the processor is triggered
> THEN any consumer using the *failure* relationship as source should receive
> the transfered data
> # GIVEN an ExecutePythonProcessorset up with both *"Script Body"* and
> *"Script File"*
> WHEN the processor is triggered
> THEN an error should be logged and neither the inline script nor the script
> body should be executed
> *Background:*
> We would like to start supporting inline python scripts in
> ExecutePythonProcessor. Someone already tried to add support for this option,
> but he did not finish the implementation.
> *Proposal:*
> The related dead code was removed in
> [PR-768|https://github.com/apache/nifi-minifi-cpp/pull/768]. The
> implementation can be started by reverting this commit. Upon implementation,
> please check if failures are handled properly and add tests for this branch
> as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
