[
https://issues.apache.org/jira/browse/NIFI-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029744#comment-17029744
]
Jerry commented on NIFI-4957:
-----------------------------
I have noticed that there hasn't been progress on this open issue (NIFI-4957).
Nevertheless I tried placing the Jolt spec in a processor group variable (e.g.
jspec) and then using this variable in the JoltTransformJSON processor ( Jolt
Specification = ${jspec} ) and it transformed the JSON FlowFile successfully.
Hence an intermediate solution (until NIFI-4957 is resolved) could be to update
the processor group variable at the cost of resetting NiFi.
I have also investigated this working process but the Jolt specification has a
*character limit*:
1.- Get Jolt Spec from file ( periodically with a CRON )
2.- Put FlowFile ( Jolt Spec ) in Distributed Map Cache with e.g. Cache Entry
Identifier = jspec
3.- Fetch Distributed Map Cache (as and when required to transform the JSON
FlowFile) and put cache value in attribute jspec
4.- Assign jspec to Jolt Specification of JoltTransformJSON processor
Will there be any progress on this open issue?
> Enable JoltTransformJSON to pickup a Jolt Spec file from a file location
> ------------------------------------------------------------------------
>
> Key: NIFI-4957
> URL: https://issues.apache.org/jira/browse/NIFI-4957
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Ryan Hendrickson
> Assignee: Ryan Hendrickson
> Priority: Minor
> Attachments: image-2018-03-09-23-56-43-912.png
>
>
> Add a property to allow the Jolt Spec to be read from a file on disk and/or
> the classpath.
> !image-2018-03-09-23-56-43-912.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
