This leads me to conclude that storm saves in batches: either the entire batch or nothing at all. So what if it saves half a batch and fails halfway. Does it know to not send the first half again or does the db need to support idempotent operations.
I do remember reading on one of the trident tutorials that it does 1 tuple per batch in some cases (I could be wrong); if that's the case then problem solved. Let me know. Thanks again -A From: [email protected] [mailto:[email protected]] On Behalf Of Nathan Marz Sent: February-19-14 6:05 PM To: [email protected] Subject: Re: trident multiput If you're using transactional states, then Trident will store the batch id with the stored values. So if there's a partial failure, only the ones with different batch ids will be updated on the next try. On Wed, Feb 19, 2014 at 12:11 PM, Adrian Mocanu <[email protected]<mailto:[email protected]>> wrote: Hi When using multiPut in Trident, my understanding is that it does a mass commit (not one by one). So if one of the changes fails, are the changes for the rows that were updated rolled back or is the user supposed to make sure all updates are idempotent so that Trident can try a few times before an error is shown? Thanks -Adrian -- Twitter: @nathanmarz http://nathanmarz.com<http://nathanmarz.com/>
