[ 
https://issues.apache.org/jira/browse/NIFI-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576708#comment-16576708
 ] 

ASF GitHub Bot commented on NIFI-5506:
--------------------------------------

Github user joewitt commented on the issue:

    https://github.com/apache/nifi/pull/2944
  
    On the PR:
    - Small things:
    1) The message has the wrong JIRA number
    2) The default of false is incorrect and should be true to remain 
consistent with current usage.
    
    Bigger concern:
    The design of NiFi security model as discussed in the previous discussion 
thread is important to consider here. Have you tested that a secure NiFi 
cluster, cluster replication, and site-to-site capabilities function in this 
configuration?  Can you elaborate on the testing conducted?  It is believed 
these would all break under this code change and configuration.
    
    We need to have a more formal feature related discussion on how to get from 
where we are to where we need to be to properly support this.  Your use case is 
a perfectly good one to support but to get there we cannot break what we do 
support today.



> 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)

Reply via email to