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

ASF GitHub Bot commented on CAMEL-11726:
----------------------------------------

GitHub user bonbonmark opened a pull request:

    https://github.com/apache/camel/pull/1919

    CAMEL-11726: Fixed the Elsql producer inconsistent behavior compared …

    Add unit test to ensure we can get header value at following step

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bonbonmark/camel CAMEL-11726

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1919.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 #1919
    
----
commit 445771214b31f3f436ab567f1deb7d2bf97d6c71
Author: Mark You <[email protected]>
Date:   2017-09-07T03:08:37Z

    CAMEL-11726: Fixed the Elsql producer inconsistent behavior compared , add 
test case to ensure we can get header value

----


> Elsql producer inconsistent behavior compare to sql component producer
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-11726
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11726
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-elsql
>    Affects Versions: 2.18.4, 2.19.1
>            Reporter: Mark You
>            Assignee: Alex Dettinger
>            Priority: Minor
>             Fix For: 2.18.5, 2.19.3, 2.20.0
>
>         Attachments: camel.png
>
>
> When using elsql component to do a insert operation, the message header is 
> losing because elsql component use exchange.getOut() to set SQL_UPDATE_COUNT 
> while sql compoent use exchange.getIn() to set SQL_UPDATE_COUNT. 
> It will cause some problem if we want to reuse header or body in next step. 
> It will be nice to change  it to use exchange.getIn() to set SQL_UPDATE_COUNT 
> as sql component which will make these two component consistent behavior. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to