Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Archival
Summary Contains details of a table archival operation.
- Attribute
Definition Represents an attribute for describing the schema for the table and indexes.
- Attribute
Value Update For the
UpdateItem
operation, represents the attributes to be modified, the action to perform on each, and the new value for each.You cannot use
UpdateItem
to update any primary key attributes. Instead, you will need to delete the item, and then usePutItem
to create a new item with new attributes.Attribute values cannot be null; string and binary type attributes must have lengths greater than zero; and set type attributes must not be empty. Requests with empty values will be rejected with a
ValidationException
exception.- Auto
Scaling Policy Description Represents the properties of the scaling policy.
- Auto
Scaling Policy Update Represents the auto scaling policy to be modified.
- Auto
Scaling Settings Description Represents the auto scaling settings for a global table or global secondary index.
- Auto
Scaling Settings Update Represents the auto scaling settings to be modified for a global table or global secondary index.
- Auto
Scaling Target Tracking Scaling Policy Configuration Description Represents the properties of a target tracking scaling policy.
- Auto
Scaling Target Tracking Scaling Policy Configuration Update Represents the settings of a target tracking scaling policy that will be modified.
- Backup
Description Contains the description of the backup created for the table.
- Backup
Details Contains the details of the backup created for the table.
- Backup
Summary Contains details for the backup.
- Batch
Statement Error An error associated with a statement in a PartiQL batch that was run.
- Batch
Statement Request A PartiQL batch statement request.
- Batch
Statement Response A PartiQL batch statement response..
- Billing
Mode Summary Contains the details for the read/write capacity mode. This page talks about
PROVISIONED
andPAY_PER_REQUEST
billing modes. For more information about these modes, see Read/write capacity mode.You may need to switch to on-demand mode at least once in order to return a
BillingModeSummary
response.- Cancellation
Reason An ordered list of errors for each item in the request which caused the transaction to get cancelled. The values of the list are ordered according to the ordering of the
TransactWriteItems
request parameter. If no error occurred for the associated item an error with a Null code and Null message will be present.- Capacity
Represents the amount of provisioned throughput capacity consumed on a table or an index.
- Condition
Represents the selection criteria for a
Query
orScan
operation:-
For a
Query
operation,Condition
is used for specifying theKeyConditions
to use when querying a table or an index. ForKeyConditions
, only the following comparison operators are supported:EQ | LE | LT | GE | GT | BEGINS_WITH | BETWEEN
Condition
is also used in aQueryFilter
, which evaluates the query results and returns only the desired values. -
For a
Scan
operation,Condition
is used in aScanFilter
, which evaluates the scan results and returns only the desired values.
-
- Condition
Check Represents a request to perform a check that an item exists or to check the condition of specific attributes of the item.
- Consumed
Capacity The capacity units consumed by an operation. The data returned includes the total provisioned throughput consumed, along with statistics for the table and any indexes involved in the operation.
ConsumedCapacity
is only returned if the request asked for it. For more information, see Provisioned capacity mode in the Amazon DynamoDB Developer Guide.- Continuous
Backups Description Represents the continuous backups and point in time recovery settings on the table.
- Contributor
Insights Summary Represents a Contributor Insights summary entry.
- Create
Global Secondary Index Action Represents a new global secondary index to be added to an existing table.
- Create
Replica Action Represents a replica to be added.
- Create
Replication Group Member Action Represents a replica to be created.
- CsvOptions
Processing options for the CSV file being imported.
- Delete
Represents a request to perform a
DeleteItem
operation.- Delete
Global Secondary Index Action Represents a global secondary index to be deleted from an existing table.
- Delete
Replica Action Represents a replica to be removed.
- Delete
Replication Group Member Action Represents a replica to be deleted.
- Delete
Request Represents a request to perform a
DeleteItem
operation on an item.- Enable
Kinesis Streaming Configuration Enables setting the configuration for Kinesis Streaming.
- Endpoint
An endpoint information details.
- Expected
Attribute Value Represents a condition to be compared with an attribute value. This condition can be used with
DeleteItem
,PutItem
, orUpdateItem
operations; if the comparison evaluates to true, the operation succeeds; if not, the operation fails. You can useExpectedAttributeValue
in one of two different ways:-
Use
AttributeValueList
to specify one or more values to compare against an attribute. UseComparisonOperator
to specify how you want to perform the comparison. If the comparison evaluates to true, then the conditional operation succeeds. -
Use
Value
to specify a value that DynamoDB will compare against an attribute. If the values match, thenExpectedAttributeValue
evaluates to true and the conditional operation succeeds. Optionally, you can also setExists
to false, indicating that you do not expect to find the attribute value in the table. In this case, the conditional operation succeeds only if the comparison evaluates to false.
Value
andExists
are incompatible withAttributeValueList
andComparisonOperator
. Note that if you use both sets of parameters at once, DynamoDB will return aValidationException
exception.-
- Export
Description Represents the properties of the exported table.
- Export
Summary Summary information about an export task.
- Failure
Exception Represents a failure a contributor insights operation.
- Get
Specifies an item and related attribute values to retrieve in a
TransactGetItem
object.- Global
Secondary Index Represents the properties of a global secondary index.
- Global
Secondary Index Auto Scaling Update Represents the auto scaling settings of a global secondary index for a global table that will be modified.
- Global
Secondary Index Description Represents the properties of a global secondary index.
- Global
Secondary Index Info Represents the properties of a global secondary index for the table when the backup was created.
- Global
Secondary Index Update Represents one of the following:
-
A new global secondary index to be added to an existing table.
-
New provisioned throughput parameters for an existing global secondary index.
-
An existing global secondary index to be removed from an existing table.
-
- Global
Secondary Index Warm Throughput Description The description of the warm throughput value on a global secondary index.
- Global
Table Represents the properties of a global table.
- Global
Table Description Contains details about the global table.
- Global
Table Global Secondary Index Settings Update Represents the settings of a global secondary index for a global table that will be modified.
- Import
Summary Summary information about the source file for the import.
- Import
Table Description Represents the properties of the table being imported into.
- Incremental
Export Specification Optional object containing the parameters specific to an incremental export.
- Input
Format Options The format options for the data that was imported into the target table. There is one value, CsvOption.
- Item
Collection Metrics Information about item collections, if any, that were affected by the operation.
ItemCollectionMetrics
is only returned if the request asked for it. If the table does not have any local secondary indexes, this information is not returned in the response.- Item
Response Details for the requested item.
- KeySchema
Element 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 oneKeySchemaElement
(for the partition key). A composite primary key would require oneKeySchemaElement
for the partition key, and anotherKeySchemaElement
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.- Keys
AndAttributes Represents a set of primary keys and, for each key, the attributes to retrieve from the table.
For each primary key, you must provide all of the key attributes. For example, with a simple primary key, you only need to provide the partition key. For a composite primary key, you must provide both the partition key and the sort key.
- Kinesis
Data Stream Destination Describes a Kinesis data stream destination.
- Local
Secondary Index Represents the properties of a local secondary index.
- Local
Secondary Index Description Represents the properties of a local secondary index.
- Local
Secondary Index Info Represents the properties of a local secondary index for the table when the backup was created.
- OnDemand
Throughput Sets the maximum number of read and write units for the specified on-demand table. If you use this parameter, you must specify
MaxReadRequestUnits
,MaxWriteRequestUnits
, or both.- OnDemand
Throughput Override Overrides the on-demand throughput settings for this replica table. If you don't specify a value for this parameter, it uses the source table's on-demand throughput settings.
- Parameterized
Statement Represents a PartiQL statement that uses parameters.
- Point
InTime Recovery Description The description of the point in time settings applied to the table.
- Point
InTime Recovery Specification Represents the settings used to enable point in time recovery.
- Projection
Represents attributes that are copied (projected) from the table into an index. These are in addition to the primary key attributes and index key attributes, which are automatically projected.
- Provisioned
Throughput Represents the provisioned throughput settings for the specified global secondary index. You must use
ProvisionedThroughput
orOnDemandThroughput
based on your table’s capacity mode.For current minimum and maximum provisioned throughput values, see Service, Account, and Table Quotas in the Amazon DynamoDB Developer Guide.
- Provisioned
Throughput Description Represents the provisioned throughput settings for the table, consisting of read and write capacity units, along with data about increases and decreases.
- Provisioned
Throughput Override Replica-specific provisioned throughput settings. If not specified, uses the source table's provisioned throughput settings.
- Put
Represents a request to perform a
PutItem
operation.- PutRequest
Represents a request to perform a
PutItem
operation on an item.- Replica
Represents the properties of a replica.
- Replica
Auto Scaling Description Represents the auto scaling settings of the replica.
- Replica
Auto Scaling Update Represents the auto scaling settings of a replica that will be modified.
- Replica
Description Contains the details of the replica.
- Replica
Global Secondary Index Represents the properties of a replica global secondary index.
- Replica
Global Secondary Index Auto Scaling Description Represents the auto scaling configuration for a replica global secondary index.
- Replica
Global Secondary Index Auto Scaling Update Represents the auto scaling settings of a global secondary index for a replica that will be modified.
- Replica
Global Secondary Index Description Represents the properties of a replica global secondary index.
- Replica
Global Secondary Index Settings Description Represents the properties of a global secondary index.
- Replica
Global Secondary Index Settings Update Represents the settings of a global secondary index for a global table that will be modified.
- Replica
Settings Description Represents the properties of a replica.
- Replica
Settings Update Represents the settings for a global table in a Region that will be modified.
- Replica
Update Represents one of the following:
-
A new replica to be added to an existing global table.
-
New parameters for an existing replica.
-
An existing replica to be removed from an existing global table.
-
- Replication
Group Update Represents one of the following:
-
A new replica to be added to an existing regional table or global table. This request invokes the
CreateTableReplica
action in the destination Region. -
New parameters for an existing replica. This request invokes the
UpdateTable
action in the destination Region. -
An existing replica to be deleted. The request invokes the
DeleteTableReplica
action in the destination Region, deleting the replica and all if its items in the destination Region.
When you manually remove a table or global table replica, you do not automatically remove any associated scalable targets, scaling policies, or CloudWatch alarms.
-
- Restore
Summary Contains details for the restore.
- S3Bucket
Source The S3 bucket that is being imported from.
- Source
Table Details Contains the details of the table when the backup was created.
- Source
Table Feature Details Contains the details of the features enabled on the table when the backup was created. For example, LSIs, GSIs, streams, TTL.
- SseDescription
The description of the server-side encryption status on the specified table.
- SseSpecification
Represents the settings used to enable server-side encryption.
- Stream
Specification Represents the DynamoDB Streams configuration for a table in DynamoDB.
- Table
Auto Scaling Description Represents the auto scaling configuration for a global table.
- Table
Class Summary Contains details of the table class.
- Table
Creation Parameters The parameters for the table created as part of the import operation.
- Table
Description Represents the properties of a table.
- Table
Warm Throughput Description Represents the warm throughput value (in read units per second and write units per second) of the table. Warm throughput is applicable for DynamoDB Standard-IA tables and specifies the minimum provisioned capacity maintained for immediate data access.
- Tag
Describes a tag. A tag is a key-value pair. You can add up to 50 tags to a single DynamoDB table.
Amazon Web Services-assigned tag names and values are automatically assigned the
aws:
prefix, which the user cannot assign. Amazon Web Services-assigned tag names do not count towards the tag limit of 50. User-assigned tag names have the prefixuser:
in the Cost Allocation Report. You cannot backdate the application of a tag.For an overview on tagging DynamoDB resources, see Tagging for DynamoDB in the Amazon DynamoDB Developer Guide.
- Time
ToLive Description The description of the Time to Live (TTL) status on the specified table.
- Time
ToLive Specification Represents the settings used to enable or disable Time to Live (TTL) for the specified table.
- Transact
GetItem Specifies an item to be retrieved as part of the transaction.
- Transact
Write Item A list of requests that can perform update, put, delete, or check operations on multiple items in one or more tables atomically.
- Update
Represents a request to perform an
UpdateItem
operation.- Update
Global Secondary Index Action Represents the new provisioned throughput settings to be applied to a global secondary index.
- Update
Kinesis Streaming Configuration Enables updating the configuration for Kinesis Streaming.
- Update
Replication Group Member Action Represents a replica to be modified.
- Warm
Throughput Provides visibility into the number of read and write operations your table or secondary index can instantaneously support. The settings can be modified using the
UpdateTable
operation to meet the throughput requirements of an upcoming peak event.- Write
Request Represents an operation to perform - either
DeleteItem
orPutItem
. You can only request one of these operations, not both, in a singleWriteRequest
. If you do need to perform both of these operations, you need to provide two separateWriteRequest
objects.
Enums§
- Approximate
Creation Date Time Precision - When writing a match expression against
ApproximateCreationDateTimePrecision
, 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. - Attribute
Action - When writing a match expression against
AttributeAction
, 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. - Attribute
Value 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.
- Backup
Status - When writing a match expression against
BackupStatus
, 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. - Backup
Type - When writing a match expression against
BackupType
, 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. - Backup
Type Filter - When writing a match expression against
BackupTypeFilter
, 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. - Batch
Statement Error Code Enum - When writing a match expression against
BatchStatementErrorCodeEnum
, 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. - Billing
Mode - When writing a match expression against
BillingMode
, 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. - Comparison
Operator - When writing a match expression against
ComparisonOperator
, 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. - Conditional
Operator - When writing a match expression against
ConditionalOperator
, 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. - Continuous
Backups Status - When writing a match expression against
ContinuousBackupsStatus
, 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. - Contributor
Insights Action - When writing a match expression against
ContributorInsightsAction
, 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. - Contributor
Insights Status - When writing a match expression against
ContributorInsightsStatus
, 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. - Destination
Status - When writing a match expression against
DestinationStatus
, 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. - Export
Format - When writing a match expression against
ExportFormat
, 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. - Export
Status - When writing a match expression against
ExportStatus
, 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. - Export
Type - When writing a match expression against
ExportType
, 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. - Export
View Type - When writing a match expression against
ExportViewType
, 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. - Global
Table Status - When writing a match expression against
GlobalTableStatus
, 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. - Import
Status - When writing a match expression against
ImportStatus
, 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. - Index
Status - When writing a match expression against
IndexStatus
, 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. - Input
Compression Type - When writing a match expression against
InputCompressionType
, 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. - Input
Format - When writing a match expression against
InputFormat
, 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. - 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. - Multi
Region Consistency - When writing a match expression against
MultiRegionConsistency
, 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. - Point
InTime Recovery Status - When writing a match expression against
PointInTimeRecoveryStatus
, 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. - Projection
Type - When writing a match expression against
ProjectionType
, 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. - Replica
Status - When writing a match expression against
ReplicaStatus
, 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. - Return
Consumed Capacity - When writing a match expression against
ReturnConsumedCapacity
, 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. - Return
Item Collection Metrics - When writing a match expression against
ReturnItemCollectionMetrics
, 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. - Return
Value - When writing a match expression against
ReturnValue
, 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. - Return
Values OnCondition Check Failure - When writing a match expression against
ReturnValuesOnConditionCheckFailure
, 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. - S3Sse
Algorithm - When writing a match expression against
S3SseAlgorithm
, 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. - Scalar
Attribute Type - When writing a match expression against
ScalarAttributeType
, 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. - Select
- When writing a match expression against
Select
, 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. - SseStatus
- When writing a match expression against
SseStatus
, 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. - SseType
- When writing a match expression against
SseType
, 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. - Stream
View Type - 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. - Table
Class - When writing a match expression against
TableClass
, 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. - Table
Status - When writing a match expression against
TableStatus
, 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. - Time
ToLive Status - When writing a match expression against
TimeToLiveStatus
, 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.