[
https://issues.apache.org/jira/browse/NIFI-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Niemiec updated NIFI-5589:
---------------------------------
Issue Type: Improvement (was: Bug)
> 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)
