Hmmmm, One small problem: While JOLTTransformJSON is quite lovely (a) it has a great "advanced" interface that allows one to test their spec and json inputs and (b) it actually works for the cases that I noted...it treats the input a single blob of JSON. Unfortunately, my input files are collections of JSON records (which--less the noted problem--JOLTTransformRecord does quite nicely with)--that's literally how they arrive, not the result of me formatting them at all.
Is there a way to get JTJ to treat the input as records? Does 1.22 or 1.23 have the fix for JTR? thx, mew On Mon, Oct 9, 2023 at 3:21 PM Mark Woodcock <[email protected]> wrote: > confirmed: version 1.21. > How recent is the fix? > > thx, > > mew > > > On Sun, Oct 8, 2023 at 11:39 PM Mark Woodcock <[email protected]> wrote: > >> Matt, >> >> Unfortunately (at home now) the details are all at work at the moment, >> but I know that I didn't start this work until April (at the earliest), so >> I'm surely using at least 1.21; is the fix more recent than that? {If so, >> perhaps there is a bug.} >> >> Fortunately, yea, JSON out is the intent; I need the data to be in that >> format to set up a subsequent transform to AVRO, so it seems there are two >> possible ways out (depending on which version I'm running): upgrade or >> change processors. So, at least there is a path. >> >> thx, >> >> mew >> >>
