[NIFI-11944] Dynamic Property Arguments strategy no longer working

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.22.0, 1.23.0
• Fix Version/s: 2.0.0-M1, 1.24.0, 1.23.1
• Labels: ExecuteStreamCommand
• Assignee: David Handermann
• Reporter: Mahieddine Cherif
• Created: 11/Aug/23 13:10
• Updated: 15/Aug/23 12:47
• Resolved: 14/Aug/23 20:35

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.

Issue Links

• is caused by: NIFI-11524 Documentation and config experience improvement for ExecuteStreamCommand
• links to: GitHub Pull Request #7607