What are the options for populating context variables? e.g. is there a
pattern to load all files from a folder, create variables based on
filename, and populate those variables with the file content?
My problem isn't reusing the transform on multiple nodes, although that may
happen in the future,
I'm resurrecting the PR to add a property to specify a file location
for the Jolt spec. In the meantime you could maintain the spec as the
value of a context variable and point to it in the Jolt Spec property.
Then you can share amongst the nodes and maintain the spec in one
place.
Regards,
Matt
Hi,
I'm hoping to be able to look at this further with someone I'm working with
who has more java background. I notice there's a reference to another PR
from Matt, so perhaps the bulk of the work has been done? What is the
status and what is the next step required?
On Thu, Feb 2, 2023 at 11:28 AM
I'm hoping to be able to look at this further with someone I'm working with
who has more java background. I notice there's a reference to another PR
from Matt, so perhaps the bulk of the work has been done? What is the
status and what is the next step required?
On Thu, Feb 2, 2023 at 11:28 AM
Hi Richard,
Some work was previously done to the similar processor JoltTransformJSON
but from what I can see, hasn't been merged into main or included in a
release.
NIFI-4957: Enable JoltTransformJSON to pickup a Jolt Spec file from a file
location
Hi,
What is the preferred way of managing the jolttransformrecord processor
specification? Is there a convenient way to store the spec in a file that
can be version controlled etc?
