Rather, I added a new strategy where you could pass arguments with a
different strategy
On June 26, 2019 at 10:25:03, Otto Fowler (ottobackwa...@gmail.com) wrote:
I fixed this in https://github.com/apache/nifi/pull/3396
On June 26, 2019 at 09:14:55, Tomislav Novosel (to.novo...@gmail.com)
I fixed this in https://github.com/apache/nifi/pull/3396
On June 26, 2019 at 09:14:55, Tomislav Novosel (to.novo...@gmail.com) wrote:
Hi all,
I have a case where I'm triggering python script with ExecuteStreamCommand
processor and one of the parameters needs to be JSON string e.g.
Also, be careful with this pattern (passing in JSON) because I think you
could hit a size limit on the total command string depending on your
platform.
On Wed, Jun 26, 2019 at 9:37 AM Mike Thomsen wrote:
> Try base64 encoding the JSON string with EL and then having Python decode
> the
Try base64 encoding the JSON string with EL and then having Python decode
the parameter.
https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#base64encode
On Wed, Jun 26, 2019 at 9:14 AM Tomislav Novosel
wrote:
> Hi all,
>
> I have a case where I'm triggering python
Hi all,
I have a case where I'm triggering python script with ExecuteStreamCommand
processor and one of the parameters needs to be JSON string e.g.
'{"foo":"bar"}', so when the script receives it, it need to convert it into
python dictionary.
The error is due to incorrect handover of parameter
