Add Support for Dedicated Read Capacity (DRN) and Metadata Schema Configuration #202
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Add Support for Dedicated Read Capacity (DRN) and Metadata Schema Configuration
Solution
This PR adds support for Dedicated Read Capacity (DRN) and Metadata Schema Configuration for serverless indexes. These features allow users to:
1. Create Serverless Index with Read Capacity and Schema
Added overloaded
createServerlessIndexmethod that accepts:ReadCapacityparameter for configuring OnDemand or Dedicated read capacityBackupModelSchemaparameter for configuring metadata schema2. Create Index for Model with Read Capacity and Schema
Added overloaded
createIndexForModelmethod that accepts:ReadCapacityparameterBackupModelSchemaparameter3. Configure Read Capacity on Existing Index
Enhanced
configureServerlessIndexmethod to accept flattened parameters for easier use:Note: Read capacity settings can only be updated once per hour per index.
Documentation
README.mdwith examples for:Type of Change
Test Plan
Added comprehensive integration tests in
ReadCapacityAndSchemaTest.java:Added helper method
waitUntilReadCapacityIsReady()inTestUtilities.javato wait for read capacity status to be "Ready" before configuring (required by API).Note: Tests for switching read capacity modes and scaling are omitted due to API rate limits (once per hour per index).