[
https://issues.apache.org/jira/browse/NIFI-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267607#comment-15267607
]
ASF GitHub Bot commented on NIFI-361:
-------------------------------------
GitHub user YolandaMDavis opened a pull request:
https://github.com/apache/nifi/pull/405
NIFI-361- Create Processors to mutate JSON data
Implementation of the TransformJSON processor using the Jolt library.
TransformJSON supports Jolt specifications for the following transformations:
Chain, Shift, Remove, Sort, Cardinality and Default. Users will be able to add
the TransformJSON processor, select the transformation they wish to apply and
enter the specification for the given transformation.
Details for creating Jolt specifications can be found
[here](https://github.com/bazaarvoice/jolt)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/YolandaMDavis/nifi NIFI-361-0.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/405.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #405
----
commit 873c534a057b051f3b28cac3cc496d59f0c352ef
Author: Yolanda M. Davis <[email protected]>
Date: 2016-04-14T12:19:41Z
NIFI-361 Adding TransformJSON from master. Also changed streams in test
since 1.7 only supported.
(cherry picked from commit ffc9d19)
----
> Create Processors to mutate JSON data
> -------------------------------------
>
> Key: NIFI-361
> URL: https://issues.apache.org/jira/browse/NIFI-361
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Aldrin Piri
> Assignee: Oleg Zhurakousky
> Priority: Minor
> Fix For: 1.0.0, 0.7.0
>
>
> Creating a separate issue to track these as a pull request has been submitted
> for related issue NIFI-356.
> Also backed by JsonPath, processors should facilitate through specification
> of user-defined properties:
> * Add - identify path and add key/value pair
> ** Handle if the path is an array, this would ignore the name specified and
> just add the value to the collection
> * Remove - delete the element at the specified path
> * Update - change the value for the given path to a provided value
> Need to determine if objects/arrays make sense for values or if they are
> needed.
> While it would be nice to be able to execute several operations per processor
> instance, it may be hard to capture all the relevant information needed for
> multiple operations in one processor configuration in a user friendly context.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
