You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Ryan Hendrickson (JIRA)" <ji...@apache.org> on 2018/08/10 00:55:00 UTC
[jira] [Updated] (NIFI-5506) Enable use of MongoDB Operators as a
NiFI Property
[ https://issues.apache.org/jira/browse/NIFI-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Hendrickson updated NIFI-5506:
-----------------------------------
Issue Type: Improvement (was: Bug)
> Enable use of MongoDB Operators as a NiFI Property
> ---------------------------------------------------
>
> Key: NIFI-5506
> URL: https://issues.apache.org/jira/browse/NIFI-5506
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.6.0, 1.7.0, 1.7.1
> Reporter: Ryan Hendrickson
> Priority: Minor
>
> Currently, the PutMongo processor allows the use of MongoDB Operators, when the query is passed in as a FlowFile to the processor. Additionally, you can also put an update query into the Property Field, however, it doesn't allow MongoDB Operators.
> This ticket is to express that a more flexible solution is needed, such that, you can update singular fields in a Mongo Document using the PutMongo processor in-line with a normal flow, vs having to create a file for it, making use of Mongo Operators and NiFi Expression Language.
>
> An example solution, could look like: A drop-down combo box in the UI that asks which Mongo Operator you'd like to use: $set, $unset, etc., then a text field supporting Expression Language for the JSON values.
>
> Example of: \{"id":"${id}", $set: \{"field1":"anything"}, would be expressed in the UI as:
>
> Mode: update
> Update Query: \{"id":"${id}"}
> Mongo Operator: $set (from DropDown)
> Operator Update Values: \{"field1":"anything"}
> Update Mode: With operators enabled
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)