[
https://issues.apache.org/jira/browse/NIFI-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345668#comment-15345668
]
Yolanda M. Davis edited comment on NIFI-2020 at 6/23/16 4:00 AM:
-----------------------------------------------------------------
This is the initial commit to enhance the JoltTransformJSON processor by
providing the ability to support custom transformations via drop in
jars/libraries.
The below describes the rules behind this enhancement:
**Case #1 – Custom Transform Selected**
In this case if the Custom option of Transform DSL is selected then 1) a Custom
Transform Class Name should be entered and 2) one or more module paths should
be provided. The Custom Transform Class Name should be a **fully qualified
classname** (e.g. eu.zacheusz.jolt.date.Dater). The Module Path can take a
comma delimited list of directory locations or one or more jar files. Once
these fields are populated the Advanced view will support validation and saving
of the specification. **A user can switch between transformation types in the
UI but not custom class names & module paths.**
**Case #2 – Chain Transformation Selected with Custom Transformations embedded**
In this case if a user wants to use one or more transforms (that include custom
transformations) in their specification then the Chainr spec option can be used
with one or more module path provides. **In this case the Custom Transform
Class Name property is not required and would be ignored (since one or more
custom transformations could be invoked in the spec).** As in Case #1 the
Advanced view will support validation and saving of specification if the
required fields are populated for this case.
was (Author: yolandamdavis):
The below describes the rules behind this enhancement:
**Case #1 – Custom Transform Selected**
In this case if Custom option is selected in the transform property then 1) a
Custom Transform Class Name should be entered and 2) one or more module paths
should be provided. The Custom Transform Class Name should be a **fully
qualified classname (fqn)** (e.g. eu.zacheusz.jolt.date.Dater). The Module Path
can take a comma delimited list of directory locations or one or more jar
files. Once these fields are populated the Advanced view will support
validation and saving of the specification. **A User can switch between
transformation types in the UI but not custom class names & module paths.**
**Case #2 – Chain Transformation Selected with Custom Transformation embedded**
In this case if a user wants to use one or more transforms (that include custom
transformations) in their specification then the Module Path should be provided
with the appropriate references to directories/libraries. **In this case the
Custom Transform Class Name property is not required and would be ignored
(since one or more custom transformations could be invoked in the spec).** As
in the above the Advanced view will support validation and saving of
specification if the required fields are populated for this case.
> 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)
