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