Hi, Sorry, I should have given a little more details. My requirement is that I have a PG (Processor Group) that I defined as a template, the PG contains several processors and one of them is a SplitJSON, I want to receive the JsonPath to be applied in a flowfile attribute.
Apparently then, I must transform my JSON before entering the PG to always find the same JsonPath. Do you consider it useful to make the change request in the processor so that in the next versions it has that functionality? On Tue, Feb 18, 2020 at 2:02 PM Pierre Villard <[email protected]> wrote: > Hi, > > We would need a bit more details about what you try to achieve (an example > maybe?) but the record processors (SplitRecord, ForkRecord, etc) might be > useful. > > Thanks, > Pierre > > Le lun. 17 févr. 2020 à 23:55, Simon Bence <[email protected]> a > écrit : > >> Hi, >> >> Without knowing the actual use case: what if you would run the JSON >> through JoltTransformJSON and convert it into a format would work well with >> the SplitJson? It might help. (On the side note: as you mention “huge” >> JSON, it might be a resource consuming operation) >> >> Regards, >> Bence >> >> On 2020. Feb 17., at 21:32, Jairo Henao <[email protected]> >> wrote: >> >> Hi all, >> >> Is there any way to be able to "split" a huge JSON, using as JsonPATH the >> value of an attribute? >> >> SplitJson processor does not support this, it must be "hard-coded" >> >> >> -- >> Jairo Henao >> >> >> -- Jairo Henao
