CreateTableRequest
¶
Source code in docs_src/capo_keyspaces/types/create_table_request.py
auto_scaling_specification
instance-attribute
¶
auto_scaling_specification: NotRequired[AutoScalingSpecification]
The optional auto scaling settings for a table in provisioned capacity mode. Specifies if the service can manage throughput capacity automatically on your behalf.
Auto scaling helps you provision throughput capacity for variable workloads efficiently by increasing and decreasing your table's read and write capacity automatically in response to application traffic. For more information, see Managing throughput capacity automatically with Amazon Keyspaces auto scaling in the Amazon Keyspaces Developer Guide.
By default, auto scaling is disabled for a table.
capacity_specification
instance-attribute
¶
capacity_specification: NotRequired[CapacitySpecification]
Specifies the read/write throughput capacity mode for the table. The options are:
-
throughputMode:PAY_PER_REQUESTand -
throughputMode:PROVISIONED- Provisioned capacity mode requiresreadCapacityUnitsandwriteCapacityUnitsas input.
The default is throughput_mode:PAY_PER_REQUEST.
For more information, see Read/write capacity modes in the Amazon Keyspaces Developer Guide.
cdc_specification
instance-attribute
¶
cdc_specification: NotRequired[CdcSpecification]
The CDC stream settings of the table.
client_side_timestamps
instance-attribute
¶
client_side_timestamps: NotRequired[ClientSideTimestamps]
Enables client-side timestamps for the table. By default, the setting is disabled. You can enable client-side timestamps with the following option:
-
status: "enabled"
Once client-side timestamps are enabled for a table, this setting cannot be disabled.
comment
instance-attribute
¶
comment: NotRequired[Comment]
This parameter allows to enter a description of the table.
default_time_to_live
instance-attribute
¶
default_time_to_live: NotRequired[DefaultTimeToLive]
The default Time to Live setting in seconds for the table.
For more information, see Setting the default TTL value for a table in the Amazon Keyspaces Developer Guide.
encryption_specification
instance-attribute
¶
encryption_specification: NotRequired[EncryptionSpecification]
Specifies how the encryption key for encryption at rest is managed for the table. You can choose one of the following KMS key (KMS key):
-
type:AWS_OWNED_KMS_KEY- This key is owned by Amazon Keyspaces. -
type:CUSTOMER_MANAGED_KMS_KEY- This key is stored in your account and is created, owned, and managed by you. This option requires thekms_key_identifierof the KMS key in Amazon Resource Name (ARN) format as input.
The default is type:AWS_OWNED_KMS_KEY.
For more information, see Encryption at rest in the Amazon Keyspaces Developer Guide.
keyspace_name
instance-attribute
¶
keyspace_name: KeyspaceName
The name of the keyspace that the table is going to be created in.
point_in_time_recovery
instance-attribute
¶
point_in_time_recovery: NotRequired[PointInTimeRecovery]
Specifies if pointInTimeRecovery is enabled or disabled for the table. The options are:
-
status=ENABLED -
status=DISABLED
If it's not specified, the default is status=DISABLED.
For more information, see Point-in-time recovery in the Amazon Keyspaces Developer Guide.
replica_specifications
instance-attribute
¶
replica_specifications: NotRequired[ReplicaSpecificationList]
The optional Amazon Web Services Region specific settings of a multi-Region table. These settings overwrite the general settings of the table for the specified Region.
For a multi-Region table in provisioned capacity mode, you can configure the table's read capacity differently for each Region's replica. The write capacity, however, remains synchronized between all replicas to ensure that there's enough capacity to replicate writes across all Regions. To define the read capacity for a table replica in a specific Region, you can do so by configuring the following parameters.
-
region: The Region where these settings are applied. (Required) -
readCapacityUnits: The provisioned read capacity units. (Optional) -
readCapacityAutoScaling: The read capacity auto scaling settings for the table. (Optional)
schema_definition
instance-attribute
¶
schema_definition: SchemaDefinition
The schemaDefinition consists of the following parameters.
For each column to be created:
-
name- The name of the column. -
type- An Amazon Keyspaces data type. For more information, see Data types in the Amazon Keyspaces Developer Guide.
The primary key of the table consists of the following columns:
-
partitionKeys- The partition key can be a single column, or it can be a compound value composed of two or more columns. The partition key portion of the primary key is required and determines how Amazon Keyspaces stores your data. -
name- The name of each partition key column. -
clusteringKeys- The optional clustering column portion of your primary key determines how the data is clustered and sorted within each partition. -
name- The name of the clustering column. -
orderBy- Sets the ascendant (ASC) or descendant (DESC) order modifier.To define a column as static use
staticColumns- Static columns store values that are shared by all rows in the same partition: -
name- The name of the column. -
type- An Amazon Keyspaces data type.
tags
instance-attribute
¶
tags: NotRequired[TagList]
A list of key-value pair tags to be attached to the resource.
For more information, see Adding tags and labels to Amazon Keyspaces resources in the Amazon Keyspaces Developer Guide.
ttl
instance-attribute
¶
ttl: NotRequired[TimeToLive]
Enables Time to Live custom settings for the table. The options are:
-
status:enabled -
status:disabled
The default is status:disabled. After ttl is enabled, you can't disable it for the table.
For more information, see Expiring data by using Amazon Keyspaces Time to Live (TTL) in the Amazon Keyspaces Developer Guide.
warm_throughput_specification
instance-attribute
¶
warm_throughput_specification: NotRequired[WarmThroughputSpecification]
Specifies the warm throughput settings for the table. Pre-warming a table helps you avoid capacity exceeded exceptions by pre-provisioning read and write capacity units to reduce cold start latency when your table receives traffic.
For more information about pre-warming in Amazon Keyspaces, see Pre-warm a table in Amazon Keyspaces in the Amazon Keyspaces Developer Guide.