Module types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that Amazon DynamoDB Streams can respond with.

Structs

• Identity

  Contains details about the type of identity that made the request.

• KeySchemaElement

  Represents a single element of a key schema. A key schema specifies the attributes that make up the primary key of a table, or the key attributes of an index.

  A KeySchemaElement represents exactly one attribute of the primary key. For example, a simple primary key would be represented by one KeySchemaElement (for the partition key). A composite primary key would require one KeySchemaElement for the partition key, and another KeySchemaElement for the sort key.

  A KeySchemaElement must be a scalar, top-level attribute (not a nested attribute). The data type must be one of String, Number, or Binary. The attribute cannot be nested within a List or a Map.

• Record

  A description of a unique event within a stream.

• SequenceNumberRange

  The beginning and ending sequence numbers for the stream records contained within a shard.

• Shard

  A uniquely identified group of stream records within a stream.

• Stream

  Represents all of the data describing a particular stream.

• StreamDescription

  Represents all of the data describing a particular stream.

• StreamRecord

  A description of a single data modification that was performed on an item in a DynamoDB table.

Enums

• AttributeValue

  Represents the data for an attribute.

  Each attribute value is described as a name-value pair. The name is the data type, and the value is the data itself.

  For more information, see Data Types in the Amazon DynamoDB Developer Guide.

• KeyType
  When writing a match expression against KeyType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• OperationType
  When writing a match expression against OperationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ShardIteratorType
  When writing a match expression against ShardIteratorType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• StreamStatus
  When writing a match expression against StreamStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• StreamViewType
  When writing a match expression against StreamViewType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.