globalSecondaryIndexes

@JvmName(name = "htmyxahyfjsvijtl")
suspend fun globalSecondaryIndexes(value: Output<List<TableGlobalSecondaryIndexArgs>>)
@JvmName(name = "lbqqbydynyxoqcod")
suspend fun globalSecondaryIndexes(value: List<TableGlobalSecondaryIndexArgs>?)

Parameters

value

Global secondary indexes to be created on the table. You can create up to 20 global secondary indexes. If you update a table to include a new global secondary index, CFNlong initiates the index creation and then proceeds with the stack update. CFNlong doesn't wait for the index to complete creation because the backfilling phase can take a long time, depending on the size of the table. You can't use the index or update the table until the index's status is `ACTIVE`. You can track its status by using the DynamoDB DescribeTable command. If you add or delete an index during an update, we recommend that you don't update any other resources. If your stack fails to update and is rolled back while adding a new index, you must manually delete the index. Updates are not supported. The following are exceptions:

  • If you update either the contributor insights specification or the provisioned throughput values of global secondary indexes, you can update the table without interruption.

  • You can delete or add one global secondary index without interruption. If you do both in the same update (for example, by changing the index's logical ID), the update fails.


@JvmName(name = "oonmlgwsughtecjr")
suspend fun globalSecondaryIndexes(vararg values: Output<TableGlobalSecondaryIndexArgs>)


@JvmName(name = "pwillmoweckoiebh")
suspend fun globalSecondaryIndexes(values: List<Output<TableGlobalSecondaryIndexArgs>>)
@JvmName(name = "ufpylkkbgvhpcoto")
suspend fun globalSecondaryIndexes(vararg values: TableGlobalSecondaryIndexArgs)

Parameters

values

Global secondary indexes to be created on the table. You can create up to 20 global secondary indexes. If you update a table to include a new global secondary index, CFNlong initiates the index creation and then proceeds with the stack update. CFNlong doesn't wait for the index to complete creation because the backfilling phase can take a long time, depending on the size of the table. You can't use the index or update the table until the index's status is `ACTIVE`. You can track its status by using the DynamoDB DescribeTable command. If you add or delete an index during an update, we recommend that you don't update any other resources. If your stack fails to update and is rolled back while adding a new index, you must manually delete the index. Updates are not supported. The following are exceptions:

  • If you update either the contributor insights specification or the provisioned throughput values of global secondary indexes, you can update the table without interruption.

  • You can delete or add one global secondary index without interruption. If you do both in the same update (for example, by changing the index's logical ID), the update fails.


@JvmName(name = "owgrtukkfgjdgbxx")
suspend fun globalSecondaryIndexes(argument: List<suspend TableGlobalSecondaryIndexArgsBuilder.() -> Unit>)
@JvmName(name = "rwhmyxrqdspehjna")
suspend fun globalSecondaryIndexes(vararg argument: suspend TableGlobalSecondaryIndexArgsBuilder.() -> Unit)
@JvmName(name = "iijerpxaobwasngs")
suspend fun globalSecondaryIndexes(argument: suspend TableGlobalSecondaryIndexArgsBuilder.() -> Unit)

Parameters

argument

Global secondary indexes to be created on the table. You can create up to 20 global secondary indexes. If you update a table to include a new global secondary index, CFNlong initiates the index creation and then proceeds with the stack update. CFNlong doesn't wait for the index to complete creation because the backfilling phase can take a long time, depending on the size of the table. You can't use the index or update the table until the index's status is `ACTIVE`. You can track its status by using the DynamoDB DescribeTable command. If you add or delete an index during an update, we recommend that you don't update any other resources. If your stack fails to update and is rolled back while adding a new index, you must manually delete the index. Updates are not supported. The following are exceptions:

  • If you update either the contributor insights specification or the provisioned throughput values of global secondary indexes, you can update the table without interruption.

  • You can delete or add one global secondary index without interruption. If you do both in the same update (for example, by changing the index's logical ID), the update fails.