[
https://issues.apache.org/jira/browse/NIFI-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403204#comment-16403204
]
ASF GitHub Bot commented on NIFI-4989:
--------------------------------------
GitHub user MikeThomsen opened a pull request:
https://github.com/apache/nifi/pull/2560
NIFI-4989 Made PutMongo able to use nested lookup keys, a query param…
… and multiple lookup keys.
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/MikeThomsen/nifi NIFI-4989
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2560.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 #2560
----
commit 380e342643885b8919599a1e8d329dfbb89600a6
Author: Mike Thomsen <mikerthomsen@...>
Date: 2018-03-17T01:51:19Z
NIFI-4989 Made PutMongo able to use nested lookup keys, a query param and
multiple lookup keys.
----
> PutMongo cannot specify nested fields or multiple lookup keys
> -------------------------------------------------------------
>
> Key: NIFI-4989
> URL: https://issues.apache.org/jira/browse/NIFI-4989
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
> Priority: Major
>
> From the user mailing list:
> {quote}{color:#222222}I am using PutMongo processor to update documents in a
> mongoDB collection.{color}
> {color:#222222}I would like to specify nested field and multiple key in the
> update Key.{color}
> {color:#222222}For exemple :{color}
> {color:#222222}- my mongodb documents are {"nom":"HAMEL",
> "prenom":"Yves",{color}
> {color:#222222}"ids":\{"idSoc":"1234", "idInterne":"788"}}{color}
> {color:#222222}- I would'd like to set update query key to something like
> {"ids.idSoc" ,{color}
> {color:#222222}"nom"}{color}
> {color:#222222}- this would means that I update document with ids.idSoc and
> nom equals to{color}
> {color:#222222}my mew document.{color}
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
