You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/09/02 08:25:00 UTC
[jira] [Commented] (CAMEL-11726) Elsql producer inconsistent
behavior compare to sql component producer
[ https://issues.apache.org/jira/browse/CAMEL-11726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151444#comment-16151444 ]
Claus Ibsen commented on CAMEL-11726:
-------------------------------------
Yeah the intention is that elsql and sql are similar.
Contributions is welcome with a patch as github PR
> 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
> Priority: Minor
> Fix For: 2.18.5, 2.20.0, 2.19.3
>
> 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)