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

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

GitHub user VijetaH opened a pull request:

    https://github.com/apache/nifi/pull/2998

    NIFI-5589 : Clarifying PutMongo documentation

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?
    
    - [ ] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
    - [ ] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Effyis/nifi master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/2998.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 #2998
    
----
commit 73af67b793eb1c3248e9f2cd42ea40ec3d5bd041
Author: Vijeta <vhingorani@...>
Date:   2018-09-12T17:19:35Z

    Clarifying upsert query documentation for PutMongo processor.

commit 063bf50f2b44610e9e66d9f2145d3f5cad7ff5f7
Author: VijetaH <vhingorani@...>
Date:   2018-09-12T17:22:35Z

    Clarifying upsert query documentation for PutMongo processor.

----


> Clarify putMongo documentation
> ------------------------------
>
>                 Key: NIFI-5589
>                 URL: https://issues.apache.org/jira/browse/NIFI-5589
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Joseph Niemiec
>            Assignee: Vijeta Hingorani
>            Priority: Minor
>
> Today the putMongoDB documentation is very vugae and leads to alot of playing 
> around to understand exactly how it works. We would improve the documentation 
> so that others can immediately start to use this processor successfully. 
>  
> My largest issues where around understanding how the UpdateQuery works, and 
> the expected content + operators that can be used when performing the update 
> with operators and not just replacing the entire document. 
>  
>  
> Here is a misc note I made on my experience doing this.
> With the putMongo processor the updateQuery is like a find() in the mongo 
> CLI, all documents that match the find will be replaced with the flowfile 
> content. The update mode has 2 choices; whole document or with operators. If 
> your updating the entire document it expects the json to be properly 
> formated. The UpdateQuery will return to this processor the documents which 
> need to be completely replaced with the incoming FlowFile content.  If your 
> using this with operators its expected that the FlowFile content ONLY be the 
> operator part you need is {$set: {"f1": "val1"} , $inc :{ "count" : 10}}, it 
> doesnt not support the find() portion that you would expect in the CLI, that 
> part is the 'UpdateQuery'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to