BatchPutItems & BatchDeleteItems now return unprocessed items/keys (previously they returned 'written records' and unit respectively)
In DynamoDB throttling conditions the batch may partially succeed and the call will return the unprocessed put/delete operations. The previous API was not exposing this, BatchPutItems in particular would return all records even if some failed.
Under the new model, the unprocessed records/keys returned can be applied directly to another batch call - this is more in line with the intent of the Dynamo API
Implements #17
DeleteItem now returns Option
Previously if DeleteItem was called with a non-existent key the call would return an 'empty' record or throw a pickler exception. This has been changed to return None - the Dynamo DeleteItem API is intended to be idempotent.
BREAKING CHANGES
BatchPutItems&BatchDeleteItemsnow return unprocessed items/keys (previously they returned 'written records' and unit respectively)In DynamoDB throttling conditions the batch may partially succeed and the call will return the unprocessed put/delete operations. The previous API was not exposing this, BatchPutItems in particular would return all records even if some failed.
Under the new model, the unprocessed records/keys returned can be applied directly to another batch call - this is more in line with the intent of the Dynamo API
Implements #17
DeleteItemnow returnsOptionPreviously if
DeleteItemwas called with a non-existent key the call would return an 'empty' record or throw a pickler exception. This has been changed to return None - the Dynamo DeleteItem API is intended to be idempotent.Implements #15