You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (Jira)" <ji...@apache.org> on 2022/02/14 17:29:00 UTC
[jira] [Updated] (NIFI-9286) As a developer, I want to add in the ability to use expression language in the Jolt tranformation processors so that I can use custom expression language to specify the jolt transformation dynamically.
[ https://issues.apache.org/jira/browse/NIFI-9286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess updated NIFI-9286:
-------------------------------
Status: Patch Available (was: Open)
> As a developer, I want to add in the ability to use expression language in the Jolt tranformation processors so that I can use custom expression language to specify the jolt transformation dynamically.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-9286
> URL: https://issues.apache.org/jira/browse/NIFI-9286
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Levi Lentz
> Assignee: Levi Lentz
> Priority: Minor
> Original Estimate: 48h
> Time Spent: 3.5h
> Remaining Estimate: 44.5h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)