[
https://issues.apache.org/jira/browse/NIFI-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368781#comment-15368781
]
ASF GitHub Bot commented on NIFI-2020:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/564
Since the test JARs are built from source code (in test/java), we're
probably fine to just include them, but I wasn't sure if there's any paperwork
needed. @joewitt Think these are fine as-is? I believe so but wanted a second
opinion. An alternative could be to set the Module Directory to point at the
target/classes directory, that should allow them to be loaded but not have to
be in a JAR.
> 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)
