You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@nifi.apache.org by Thad Guidry <th...@gmail.com> on 2016/01/31 04:56:36 UTC

Mapping from JMS -> JSON -> SQL

Any best practices on how to map fields from a JMS source into JSON (for
some validation stuff perhaps with ExecuteScript and Groovy) and finally
into MySQL with NiFi ?

How do folks usually do field mapping in NiFi between an input and output ,
in general ?

Thad
+ThadGuidry <https://www.google.com/+ThadGuidry>

Re: Mapping from JMS -> JSON -> SQL

Posted by Matt Burgess <ma...@gmail.com>.

If the JMS source is actual JSON then you can use EvaluateJsonPath (or SplitJson for arrays), you can craft the attributes to match the arguments to PutSql and have a prepared statement within... I think :)

ExecuteScript will be for those times you just can't presently connect the dots with existing processors. It's slower (and naughty?) by nature :)

Regards,
Matt

Sent from my iPhone

> On Jan 30, 2016, at 10:56 PM, Thad Guidry <th...@gmail.com> wrote:
> 
> Any best practices on how to map fields from a JMS source into JSON (for some validation stuff perhaps with ExecuteScript and Groovy) and finally into MySQL with NiFi ?
> 
> How do folks usually do field mapping in NiFi between an input and output , in general ?
> 
> Thad
> +ThadGuidry