Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 4 Nov 2016 15:55:58 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.13017617.1478176858000.190877.1478274958727@Atlassian.JIRA>
In-Reply-To: <JIRA.13017617.1478176858000@Atlassian.JIRA>
References: <JIRA.13017617.1478176858000@Atlassian.JIRA> <JIRA.13017617.1478176858296@arcas>
Subject: [jira] [Commented] (CAMEL-10444) Return header with key
 CamelMongoDbRecordsAffected from update and remove operations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 04 Nov 2016 15:56:00 -0000


    [ https://issues.apache.org/jira/browse/CAMEL-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636793#comment-15636793 ] 

Claus Ibsen commented on CAMEL-10444:
-------------------------------------

A github PR is welcome
http://camel.apache.org/contributing

> 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
>
> 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)