This might be more of a question for the dev mailing list, but does it make
sense to have a 'SplitCSV' processor?
A situation we encounter a lot at Interset are CSV files whose records
extend across multiple lines, similar to Prabhu's data.
We currently have code written for Flume for isolating m
sto.apa...@gmail.com *
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> On Feb 17, 2017, at 9:15 AM, Joe Witt wrote:
>
> Wes
>
> Absolutely yes. Would be a very welcome contribution and is such a common
> case.
>
> Thanks
> Joe
>
>
Hey Alessio,
I've only used the ExecuteScript processor once before, but the one thing I
noticed was the session wasn't being commited after the transfer (
session.commit()). If you add that after the transfers on lines 23 and 26,
does that make a difference?
Also, what's the timer strategy for t
I just wanted to confirm something, but I couldn't find anything online.
A lot of docs that talk about setting NiFi up from a System Admin's
point-of-view, mention changing config to move several folders out of the
NiFi root dir. These typically include all 4 repositories, as well as files
like th
You may have to use 1.3's 'UpdateRecord'.
You can set the 'Replacement Value Strategy' to 'Record Path Value', and
add a custom property of key '/attributes/baz' with a value of '/baz'.
That should convert from the input to output schemas.
--Wes
On Wed, Jun 14, 2017 at 2:57 PM, Mika Borner wro
Hey Pat,
Give this spec a try;
"arr": {
"*": "=toString"
},
"val": {
"*": {
"*": "=toString"
}
}
This site here (links specifically to a type conversion demo) is useful for
testing JOLT specs against an input;
https://jolt-demo.appspot.com/#modify-typeConversion
On Fri, Aug 25, 2017
