[
https://issues.apache.org/jira/browse/NIFI-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368789#comment-15368789
]
ASF GitHub Bot commented on NIFI-2020:
--------------------------------------
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/564#discussion_r70157534
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/JoltTransformJSON.java
---
@@ -95,6 +99,24 @@
.required(false)
.build();
+ public static final PropertyDescriptor CUSTOM_CLASS = new
PropertyDescriptor.Builder()
+ .name("jolt-custom-class")
+ .displayName("Custom Transformation Class Name")
+ .description("Fully Qualified Class Name for Custom
Transformation Module Directory should be specified")
+ .required(false)
+ .expressionLanguageSupported(false)
--- End diff --
Any reason why EL is not supported? I can't think of a great use case for
using EL here, but unless there's a good reason not to, it adds to the
flexibility of the system (and could eventually benefit from the Variable
Registry right?)
> Enhance JoltTransformJSON processor to support custom transforms
> ----------------------------------------------------------------
>
> Key: NIFI-2020
> URL: https://issues.apache.org/jira/browse/NIFI-2020
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Yolanda M. Davis
> Assignee: Yolanda M. Davis
> Fix For: 1.0.0
>
>
> Jolt supports additional custom transforms via fully-qualified Java
> classnames. Would like to provide the ability to support custom
> transformation (via drop in jars) for the Jolt Transform processor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
