-
Notifications
You must be signed in to change notification settings - Fork 910
DynamoDbEnhancedClient: Delete table operation #1966
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thank you for reaching out @alexfuksenko-toast, marking as a feature request. |
Similarly, other table-level operations also seem to be missing from the v2 API, e.g. "describe table". |
+1 |
Are there any plans on implementing support for deleteTable operation yet? |
No timeline for it yet, will comment here when we have an update. |
DeleteTable is now available in DynamoDbTable, released in SDK version |
|
…fd4269dc1 Pull request: release <- staging/ad21a762-06dd-4792-af67-eeffd4269dc1
Uh oh!
There was an error while loading. Please reload this page.
The DynamoDbEnhancedClient returns a DynamoDbTable that allows you to do various dynamodb operations, including createTable(), but there is no way to delete the table.
This means for repeated cases, especially for integration tests, I need to maintain a DynamoDbClient and a DynamoDbEnhancedClient reference.
Even the enhanced client unit tests need to use a the normal client for only delete table operations like:
https://github.com/aws/aws-sdk-java-v2/blob/master/services-custom/dynamodb-enhanced/src/test/java/software/amazon/awssdk/enhanced/dynamodb/functionaltests/AsyncBasicQueryTest.java#L139
Describe the Feature
I think it would be nice if the DynamoDbEnhancedClient was able to delete tables itself, either through the table reference or through the enhanced client
Is your Feature Request related to a problem?
Awkward to create two different DynamoDbClients (enhanced and regular for usage)
Proposed Solution
Describe alternatives you've considered
Additional Context
Your Environment
The text was updated successfully, but these errors were encountered: