It need be _id. In case of it being generated automatically, it will be
tough to keep track. It can be any valid MongoDB filter query, if I’m
right. So the query should be:
{
,
“$set” : {
“FieldA” : “New FieldA value”
}
}
On Fri, 16 Mar 2018 at 5:07 PM, Mike Thomsen
I noticed that your update document didn't have an update key in it. The
default lookup key is _id so you'd need something like this:
{
"_id": "ID_HERE",
"$set": {
"new_field": 1
}
}
On Wed, Jan 10, 2018 at 6:05 AM, fabe_bdx wrote:
> Dear Pierre,
>
>
Dear Pierre,
First all many thnaks for your help, we were able to use the copy you
provided us and restart Nifi with 1.5.0 module.
But it's appear that don't realy work like expected.
If we try to update some attributes with the $set commant it don't work.
*Original MongoDb record :*
{
Yes, if you have a running 1.5.0-SNAPSHOT NiFi running, then you could get
the NAR from the lib directory and just drop it into the directory in your
1.3 instance. Note that it's not recommended to put custom NARs into the
lib directory. Best is to define an external directory for custom NARs in
Thanks for the repply, but i don't have any knowledge to complile NAR object
:/
is it possible to extract them of 1.5.0 and push it into nifi 1.3.0 directly
?
Thx,
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Hi,
Easiest solution is probably to build the Mongo NAR with 1.5.0 code, and
drop it into your NiFi 1.3. This way you'll have the two versions of the
processor available in NiFi and you can easily switch from one version of
the processor to another.
Hi All,
We actually used nifi 1.3.0, with a PutMongo 1.3.0 processor, we have an
issue with the upsert capabilities of this processor.
During the Upsert if an attribute of the document is not present in the
request from putmongo, the processor suppress it the mongo document
collection.
We