camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11726) Elsql producer inconsistent behavior compare to sql component producer
Date Wed, 06 Sep 2017 19:46:00 GMT

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

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

Github user aldettinger closed the pull request at:

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


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

Mime
View raw message