[
https://issues.apache.org/jira/browse/NIFI-11944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahieddine Cherif updated NIFI-11944:
-------------------------------------
Description:
It appears that since the latest refactoring of the ExecuteStreamCommand
processor, a regression has been introduced.
When one sets the arguments strategy to "Dynamic Property Arguments", it is
still interpreted as Command Argument.
So concretely not only the processor doesn't build the command property but
also emits continuously warnings (As if one have set dynamic properties without
choosing the appropriate strategy which is not the case)
ExecuteStreamCommand[id=e43875bb-0189-1000-0000-000016ec126f] [Command
Arguments Strategy] should be set to [Dynamic Property Arguments] when command
arguments are supplied as Dynamic Properties. The property [command.argument.1]
will be ignored.
*Bug Reproducer :*
It is really easy to replicate, just pull the ExecuteStreamCommand processor,
set CommandArgumentStrategy to Dynamic Property Argument, in command set for
instance cat and a dynamic property command.argument.1 => *
I've attached a reproducer here a small flow that replicate the issue.
was:
It appears that since the latest refactoring of the ExecuteStreamCommand
processor, a regression has been introduced.
When one sets the arguments strategy to "Dynamic Property Arguments", it is
still interpreted as Command Argument.
So concretely not only the processor doesn't build the command property but
also emits continuously warnings (As if one have set dynamic properties without
choosing the appropriate strategy which is not the case)
ExecuteStreamCommand[id=e43875bb-0189-1000-0000-000016ec126f] [Command
Arguments Strategy] should be set to [Dynamic Property Arguments] when command
arguments are supplied as Dynamic Properties. The property [command.argument.1]
will be ignored.
*Reproducer :*
It is really easy to replicate, just pull the ExecuteStreamCommand processor,
set CommandArgumentStrategy to Dynamic Property Argument, in command set for
instance cat and a dynamic property command.argument.1 => *
I've attached a reproducer here a small flow that replicate the issue.
> Dynamic Property Arguments strategy no longer working
> -----------------------------------------------------
>
> Key: NIFI-11944
> URL: https://issues.apache.org/jira/browse/NIFI-11944
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.19.0, 1.20.0, 1.21.0, 1.22.0, 1.23.0
> Reporter: Mahieddine Cherif
> Priority: Major
> Labels: ExecuteStreamCommand
> Attachments: DynamicPropertyIssue.json, Screenshot 2023-08-11 at
> 15.09.35.png
>
>
> It appears that since the latest refactoring of the ExecuteStreamCommand
> processor, a regression has been introduced.
> When one sets the arguments strategy to "Dynamic Property Arguments", it is
> still interpreted as Command Argument.
> So concretely not only the processor doesn't build the command property but
> also emits continuously warnings (As if one have set dynamic properties
> without choosing the appropriate strategy which is not the case)
> ExecuteStreamCommand[id=e43875bb-0189-1000-0000-000016ec126f] [Command
> Arguments Strategy] should be set to [Dynamic Property Arguments] when
> command arguments are supplied as Dynamic Properties. The property
> [command.argument.1] will be ignored.
> *Bug Reproducer :*
> It is really easy to replicate, just pull the ExecuteStreamCommand processor,
> set CommandArgumentStrategy to Dynamic Property Argument, in command set for
> instance cat and a dynamic property command.argument.1 => *
> I've attached a reproducer here a small flow that replicate the issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
