agh yes... that makes sense.
Thanks Matt!
On Tue, Feb 28, 2023 at 11:23 AM Matt Burgess wrote:
> Philip,
>
> Those are OUT parameters so ExecuteSQL/PutSQL doesn't know how to get
> the values out after calling the procedure. We'd likely want a
> separate processor like ExecuteStoredProcedure an
Philip,
Those are OUT parameters so ExecuteSQL/PutSQL doesn't know how to get
the values out after calling the procedure. We'd likely want a
separate processor like ExecuteStoredProcedure and would have to
figure out how to handle OUT parameters, maybe adding those fields to
the outgoing records o
Thanks for replies...
I'm trying putSQL to call the following stored-procedure...
CREATE OR REPLACE PROCEDURE SMV.RUN_ALL_PS
(IN IN_RESET CHAR(1), -> This will always be
'N" when called from nifi
OUT OUT_SQLSTATE CHAR(5).
OUT OUT_RETURN_CODEI
Using NiFi 1.18.0/1.20.0 and trying to run a Groovy Script to access a
Hazelcast 3.9 cluster with a composite Java key.
I started with Matt Burgess' link
(http://funnifi.blogspot.com/2016/02/executescript-using-modules.html) to try
and work through the Hazelcast connection via Groovy. It appear
