Perform a batch delete operation using the given key -> value pairs.
Perform a batch delete operation using the given key -> value pairs. DynamoDB has the following restrictions:
Perform a batch put operation using the given key -> value pairs.
Perform a batch put operation using the given key -> value pairs. DynamoDB has the following restrictions:
takes a Range Key
Write a value using the supplied update mode semantics.
Write a value using the supplied update mode semantics.
Note that replace mode only works correctly if you supply an old value to replace.
Contains functions that perform operations on a DynamoDB table. Functions return a DynamoDBAction that can be run by providing an instance of an AmazonDynamoDBClient (see AmazonClient for convenient constructor functions).
This class is generally not intended to be used directly, but used through the Table algebra with column definitions.
Tables are represented as key-value mappings, so you need classes to represent the key and the value. In addition, you need to create instances of: * TODO describe new Column based definition * Table - specify the key, value, hash key and range key types, and a TableDefinition (which includes a name, the key types, and a couple of other DynamoDB parameters). * Columns - Columns map your Scala types into columns in DynamoDB i.e. start with a Column with a name for each column in DynamoDB, and then create composite columns using Column.composeX to be able to map your high-level Scala classes. * Encoders/Decoders - Under the covers, we use Encoders/Decoders to convert 'primitive' or low-level Scala types into suitable values for DynamoDB (ints, strings, dates). In most cases you don't need to be concerned with Encoders/Decoders (they will be picked up automatically in your Column definition). However, you you can extend the standard set if you need to.