Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
In the current jolt processors (both the joltJSON and JoltRecord), they are inflexible when it comes to custom transformation specification because of the lack of expression language support. Additionally, the dynamic modification of the classpath is not implemented correctly, leading to issues in specifying a custom transform method in a jar-file as outlined in NIFI-6213.
This ticket will add the above functionality and address the issues outlined in NIFI-6213.
Attachments
Issue Links
- fixes
-
NIFI-6213 Custom Transformation Class not found with JoltTransformJSON Processor
- Resolved
- links to