[
https://issues.apache.org/jira/browse/NIFI-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247138#comment-15247138
]
ASF GitHub Bot commented on NIFI-361:
-------------------------------------
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/354#issuecomment-211718256
@joewitt As I am thinking more about it, you have a point for @OnStopped,
so I am retracting my comment. As for volatile, what's at question is the
visibility of the _transformer_ by another thread. Basically if T1 executed
@OnSchedule where it is set to a value, T2 may come in and it will still be
null, not because of some race condition, but simply because the value set by
T1 may not be visible by T2.
> 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)
