Member since
07-30-2019
3427
Posts
1632
Kudos Received
1011
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 91 | 01-27-2026 12:46 PM | |
| 499 | 01-13-2026 11:14 AM | |
| 1079 | 01-09-2026 06:58 AM | |
| 927 | 12-17-2025 05:55 AM | |
| 988 | 12-15-2025 01:29 PM |
04-12-2023
07:52 AM
2 Kudos
@drewski7 The removal of quotes from the "command arguments" is expected behavior in the ExecuteStreamCommand processor. This processor was introduced to NiFi more than 10 years ago and was originally designed for a more minimal scope of work including the expectation that FlowFile content would be passed to the script/command being executed. As time passed on the use cases that were trying to be solutioned via the ExecuteStreamCommand expanded; however, handling those use case would potential break users already implemented and working dataflow. So rather then change that default behavior, a new property "Command Arguments Strategy" was added with the original "Command Arguments Property" as the default (legacy method) and a new "Dynamic property arguments" option. This change is part of this JIra and implemented as of Apache NiFi 1.10: https://issues.apache.org/jira/browse/NIFI-3221 In your use case, you'll want to switch to using the "Dynamic property arguments". This will then require you to click on the "+" to add a new dynamic property. The property names MUST use this format: command.argument.<num> So in your case you might try something like: command.argument.1 = -X POST -H referer:${Referer} -H 'Content-Type: application/json' -d '{"newTopics": [{"name":"testing123","numPartitions":3,"replicationFactor":3}], "allTopicNames":["testing123"]}' --negotiate -u : -b /tmp/cookiejar.txt -c /tmp/cookiejar.txt http://SMM-HOSTNAME:8585/api/v1/admin/topics If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt
... View more
04-12-2023
05:45 AM
Ok, now that makes sense. I downloaded from the official repository Index of /dist/nifi (apache.org) and I'm using version 1.13.2 (due to some project requirements)
... View more
04-11-2023
05:00 AM
Hello Bakho, did Matt's recommendation/suggestion solve your problem? I am having the same issue using certificates created by the NiFi Toolkit.
... View more
04-10-2023
01:33 PM
@ahmedalsaidi You do not need to change the content type since you specify the character set to use in the ExtractText processor which defaults to "UTF-8". If you change the content type or the filename, the built in content viewer in NiFi would be able to display text instead of hex. For example: adding ".txt" to end of filename. When it comes to your matching issue, it would be difficult for me to say what is happening here without a working and non-working sample to look at. In Java regular expressions the "." means any character; however, looking at you hex output screenshot it looks like you really want a literal "." to match. If you want your java regular expression to match the literal ".", then add a "\" (backslash) before each ".". If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt
... View more
04-10-2023
06:28 AM
Switching to a new version of NiFi solved the problem.
... View more
04-10-2023
05:38 AM
@Dave0x1 have you been able to resolved your issue. If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
... View more
04-06-2023
11:36 PM
Thanks for support @MattWho . I overlooked that sticky session part but after configuring the sticky session on the load balancer everything is working fine.
... View more