You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating secondary indexes, DynamoDB can take a significant random time, even on an empty database. On one hash_key only index (no range key) I am waiting for about 2-3 minutes until it exits the backfilling state.
When you want to create data in a migration which depends on the new index, this is bad.
For creating a table, there's a handy Waiter in the Gem, but that only works on table_exists and table_not_exists.
When using the AWS CLI, I can get the index status:
Thanks for the feature request. This unfortunately is an upstream request to the dynamodb team who owns the modeling which includes waiters. I can't guarantee delivery or timeline of these.
Describe the feature
When creating secondary indexes, DynamoDB can take a significant random time, even on an empty database. On one hash_key only index (no range key) I am waiting for about 2-3 minutes until it exits the backfilling state.
When you want to create data in a migration which depends on the new index, this is bad.
For creating a table, there's a handy Waiter in the Gem, but that only works on table_exists and table_not_exists.
When using the AWS CLI, I can get the index status:
It would be great if that waiter would be available natively in the SDK.
Use Case
Creating data which depends on the existance of a new secondary index.
Proposed Solution
No response
Other Information
No response
Acknowledgements
SDK version used
latest
Environment details (OS name and version, etc.)
latest
The text was updated successfully, but these errors were encountered: