[
https://issues.apache.org/jira/browse/CAMEL-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15639490#comment-15639490
]
ASF GitHub Bot commented on CAMEL-10444:
----------------------------------------
GitHub user nickbusy opened a pull request:
https://github.com/apache/camel/pull/1250
CAMEL-10444: return header CamelMongoDbRecordsAffected
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickbusy/camel CAMEL-10444
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1250.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 #1250
----
commit 191f1b93f8851a4f97b9988e6f546a90d732a3d1
Author: Nick Busy <[email protected]>
Date: 2016-11-05T05:30:22Z
CAMEL-10444: return header CamelMongoDbRecordsAffected from update and
remove operations
----
> Return header with key CamelMongoDbRecordsAffected from update and remove
> operations
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-10444
> URL: https://issues.apache.org/jira/browse/CAMEL-10444
> Project: Camel
> Issue Type: Improvement
> Components: camel-mongodb
> Affects Versions: 2.18.0
> Reporter: Nick Busy
> Priority: Minor
> Fix For: 2.18.1, 2.19.0
>
>
> Since release 2.18 MongoDB component does not return a header with key
> CamelMongoDbRecordsAffected (MongoDbConstants.RECORDS_AFFECTED constant)
> after completing operations update and delete. This is a breaking change but
> can easily be patched in MongoDbProducer class.
> It's probably more a bug report rather than feature request depending on if
> the change was by design.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
