[
https://issues.apache.org/jira/browse/NIFI-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen updated NIFI-4759:
-------------------------------
Description:
Two issues:
* The updateKey field is ignored in favor of _id in the update code block of
PutMongo.
* _id fields are always treated as strings, even if they're valid ObjectIds
represented as a string. PutMongo should be able to handle these as ObjectIds.
Regarding the first point, this works:
{code:java}
{
"_id": "1234",
"$set": { "msg": "Hello, world" }
}
{code}
This does not:
{code:java}
{
"uniqueKey": "12345",
"$set": { "msg": "Hello, World" }
}
{code}
was:
Two issues:
* The updateKey field is ignored in favor of _id in the update code block of
PutMongo.
* _id fields are always treated as strings, even if they're valid ObjectIds
represented as a string. PutMongo should be able to handle these as ObjectIds.
This works:
{code:java}
{
"_id": "1234",
"$set": { "msg": "Hello, world" }
}
{code}
This does not:
{code:java}
{
"uniqueKey": "12345",
"$set": { "msg": "Hello, World" }
}
{code}
> PutMongo does not handle updateKey field correctly
> --------------------------------------------------
>
> Key: NIFI-4759
> URL: https://issues.apache.org/jira/browse/NIFI-4759
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
>
> Two issues:
> * The updateKey field is ignored in favor of _id in the update code block of
> PutMongo.
> * _id fields are always treated as strings, even if they're valid ObjectIds
> represented as a string. PutMongo should be able to handle these as ObjectIds.
> Regarding the first point, this works:
> {code:java}
> {
> "_id": "1234",
> "$set": { "msg": "Hello, world" }
> }
> {code}
> This does not:
> {code:java}
> {
> "uniqueKey": "12345",
> "$set": { "msg": "Hello, World" }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
