Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
From: "Siano, Stephan" <stephan.siano@sap.com>
To: "users@camel.apache.org" <users@camel.apache.org>
Subject: RE: IdempotentConsumer Query (How does it work)
Thread-Topic: IdempotentConsumer Query (How does it work)
Thread-Index: AQHRUdZ7X92Gi3yfkEG1lJF84r6aKJ8BDPOA
Date: Mon, 18 Jan 2016 10:16:21 +0000
Message-ID: <bb1bcb7a609d4a9c81b03770c930d168@derote13de02.global.corp.sap>
References: <1453110958338-5776387.post@n5.nabble.com>
In-Reply-To: <1453110958338-5776387.post@n5.nabble.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,

The idempotent consumer is not supposed to work on the exchangeId (a new on=
e will be generated for each file) but on an identifier from the payload or=
 some metadata that is unique for the file. One possibility would be that t=
he payload itself contains a unique order id or something like that. In tha=
t case you want to process the order only once.

If you do not have such an entity in your data file, this might become diff=
icult. If you are reading files and split them into lines and the filenames=
 are globally unique (which means that you will never reuse a filename) it =
might be possible to get a unique identifier for a line with a clever conca=
tenation of CamelFileName and CamelSplitIndex (you must put something in be=
tween that is not used in the filename in order to avoid clashes (foo11 cou=
ld be filename foo and index 11 or filename foo1 and index 1)).

Best regards
Stephan

-----Original Message-----
From: fxthomas [mailto:felix.thomas@gmail.com]=20
Sent: Montag, 18. Januar 2016 10:56
To: users@camel.apache.org
Subject: IdempotentConsumer Query (How does it work)

hello, =20

    I had read the doc at http://camel.apache.org/idempotent-consumer.html.=
=20
I have a doubt on how it maintains the uniqueness . I checked the code in
DefaultExchange and saw the ExchangeID generated using Instance, Prefix etc=
.
But I am not sure How it makes the message ID unique and avoid duplicates .=
 =20

For example :-=20
In my case  I have to read a CSV file and process it. But in case of an
exception or IO error if the route stops and if I restart the route again i=
t
should start from the line in CSV which was not read earlier and not
processed.  The already processed lines should be skipped or ignored since
they will be duplicates . I thought  of using JDBC based IdempotentConsumer
. But I am not sure if it will work fine in this scenario .

Any pointer will be helpful to understand.


--
View this message in context: http://camel.465427.n5.nabble.com/IdempotentC=
onsumer-Query-How-does-it-work-tp5776387.html
Sent from the Camel - Users mailing list archive at Nabble.com.