[
https://issues.apache.org/jira/browse/NIFI-11524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747150#comment-17747150
]
Josh Anderton commented on NIFI-11524:
--------------------------------------
I think this may have created a bug when using Dynamic Property Arguments. We
just upgraded to v1.22.0 and are getting lots of warnings on all of the
processors that use this strategy.
ExecuteStreamCommand[id=xxx] [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.
Even though the "Command Arguments Strategy" property is set to "Dynamic
Property Arguments", we continuously receive warnings. It does not appear to
be impacting the actual functionality of the processor from what I have
observed so far, only excessive warnings in the logs and bulletin board.
> Documentation and config experience improvement for ExecuteStreamCommand
> ------------------------------------------------------------------------
>
> Key: NIFI-11524
> URL: https://issues.apache.org/jira/browse/NIFI-11524
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation & Website, Extensions
> Reporter: Nandor Soma Abonyi
> Assignee: Nandor Soma Abonyi
> Priority: Major
> Fix For: 2.0.0, 1.22.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This PR indends to add documentation for the ExecuteSteamCommand processor
> and improves the configuration experience by adding dependency between
> properties.
> I've noticed that the processor adds every Dynamic Property as environment
> variable even when it is a command argument. I didn't change this behavior
> because it might introduce a breaking change, but I'd change this behavior in
> a separate 2.0 only PR. Simply adding another regex check there would
> introduce the 4. regex check which is quite ugly so it would be a good
> opportunity for refactor. Another option would be to add validation for
> environment variables to ensure they don't contain {{{}.{}}}character,
> because most shells don't support it. But I'm not sure about that because
> there are commands that can utilize such env variables even though they are
> not common.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
